siesa-agents@2.1.106
Paquete para instalar y configurar agentes SIESA en tu proyecto
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe postinstall hook automatically installs or updates first-party agent configuration in the consumer's working tree. This matches the warning category for package-owned agent setup; the inspected source does not establish a separate concrete attack chain.
Decision evidence
public snapshot- package.json runs the installer from postinstall, and the installer entrypoint calls its install routine.
- The installer targets the current working directory and copies packaged mappings there; mappings include project agent configuration paths such as .claude and .github.
- The installer documents a merge for .mcp.json that preserves user-added MCP entries.
- The observability helper targets the home Claude configuration directory and writes placeholder telemetry values.
- The Jira helper reads project-local OAuth tokens and posts refresh requests to Atlassian's token endpoint.
Source & flagged code
18 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.106.
See all versions of siesa-agents for other recorded verdicts.
- Review the evidence and your use of siesa-agents@2.1.106 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.