siesa-agents@2.1.108
Paquete para instalar y configurar agentes SIESA en tu proyecto
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe verified postinstall performs automatic first-party agent setup, which fits the warning-only agent extension lifecycle risk. The inspected OAuth and observability code does not establish a separate attack.
Decision evidence
public snapshot- package.json runs bin/install.js during postinstall.
- The installer copies package mappings into its working directory; its standard path runs installation or update.
- The mappings include the package-owned .claude directory.
- The installer describes .mcp.json updates as preserving custom MCP entries.
- The observability helper targets ~/.claude/observability/.env; its --check mode is read-only.
- The Jira OAuth flow targets auth.atlassian.com, and the Jira client locates its token and configuration files in the project.
- The inspected behavior supports a warning for automatic first-party agent setup, but does not establish credential theft or another active attack.
- The observability helper handles placeholder settings, and the inspected Jira authentication flow uses Atlassian endpoints.
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.108.
See all versions of siesa-agents for other recorded verdicts.
- Review the evidence and your use of siesa-agents@2.1.108 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.