siesa-agents
Paquete para instalar y configurar agentes SIESA en tu proyecto
This report shows the evidence for siesa-agents@2.1.104. 8 of 11 known versions are blocked or flagged. The newest version, 2.1.108, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic postinstall performs unconsented, overwrite-enabled mutation of broad AI-agent control surfaces. This is concrete install-hook abuse under the stated policy.
Decision evidence
public snapshot- The package automatically runs its installer after npm installation.
- The installer copies package content into the consumer project with overwrite enabled.
- The mapped destinations include Claude, Gemini, MCP, VS Code, and GitHub control directories.
- The automatic installer initializes Git and clones a remote repository into the consumer project.
- No runtime dependency on this package name was declared.
- The inspected remote clone target is a named GitHub repository rather than an opaque payload URL.
Source & flagged code
20 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to siesa-agents@2.1.104.
The versions list below shows the verdict for each recorded version.
- Avoid installing siesa-agents@2.1.104. 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.