siesa-agents@2.1.107
Paquete para instalar y configurar agentes SIESA en tu proyecto
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe automatic lifecycle setup creates an agent extension lifecycle risk because it copies agent assets without first requiring an explicit setup command. The inspected OAuth flow uses Atlassian endpoints and local token storage; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json runs bin/install.js from an automatic postinstall hook.
- The installer uses its current working directory as the target for package content.
- The installer maps package-owned agent assets to paths including .github and .claude.
- On a new installation, the installer copies mapped assets to their target paths.
- The installer also clones a Siesa design repository into _bmad-output/design-artifacts.
- Reviewed OAuth code sends authorization and refresh exchanges to Atlassian and saves returned tokens locally.
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.107.
See all versions of siesa-agents for other recorded verdicts.
- Review the evidence and your use of siesa-agents@2.1.107 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.