@speranto/speranto@0.4.0
A quick and simple machine translation tool for i18n in webapps. Translate JSON, JS/TS, Markdown files and database content using OpenAI, Mistral, or Ollama.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package performs unconsented postinstall mutation of consumer AI-agent instruction files, directing agents to follow package-provided guidance. This is a concrete AI-agent control-surface change and meets the blocking policy.
Decision evidence
public snapshot- package.json runs the agent-docs installer from postinstall.
- The installer invokes the manager with postinstall enabled for a consumer project that directly depends on the package.
- The manager targets consumer AGENTS.md and CLAUDE.md instruction files.
- It inserts a managed instruction directing agents to read and follow the package guide, then writes changed instruction files and the guide into the consumer project.
- The inserted block is bounded by Speranto-specific markers and its instruction concerns localization and Speranto configuration.
- The installer skips the package’s own project and can be disabled with SPERANTO_SKIP_AGENT_DOCS.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs the agent-docs installer from postinstall.
package.jsonView on unpkg · L36Package source references dynamic require/import behavior.
dist/index.mjsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @speranto/speranto@0.4.0.
See all versions of @speranto/speranto for other recorded verdicts.
- Avoid installing @speranto/speranto@0.4.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.