registry / AI-agent control-surface risk / agile-sddf
agile-sddf
Agile Spec-Driven-Development Framework for AI agents
This report shows the evidence for agile-sddf@2.0.3. 3 of 13 known versions are blocked or flagged. The newest version, 4.1.0, is allowed. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic lifecycle hook writes package-authored agent definitions into a consumer or home AI-agent directory. This meets the blocking policy for unconsented postinstall mutation of a foreign or broad AI-agent control surface.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation, including postinstall execution
Impact
The package changes an AI-agent control surface without an explicit user command or consent.
Mechanism
Automatic copying of packaged agent and skill definitions into .claude
Policy narrative
The package declares postinstall, which calls its installer automatically. That installer selects the consumer project's .claude directory by default and copies its bundled skills and agents there; global npm installs target the user's home directory. This is an unconsented install-time mutation of an AI-agent control surface.
AI rationale
The automatic lifecycle hook writes package-authored agent definitions into a consumer or home AI-agent directory. This meets the blocking policy for unconsented postinstall mutation of a foreign or broad AI-agent control surface.
Evidence
package.jsonscripts/postinstall.jsscripts/install.js.claude/skills.claude/agents~/.claude/skills~/.claude/agents
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 99.0% confidence with low false-positive risk.
Evidence for policy risk
- The manifest automatically runs a postinstall script.
- The postinstall script installs into .claude without asking the user.
- The installer targets the consuming project or, for global installs, the user home directory.
- The installer copies the package's skills and agents into that AI-agent control directory.
Evidence against
- No network, credential harvesting, shell execution, or self-dependency was found in the executable scripts.
- The flagged Python file is a plain test fixture with an intentional failing assertion, not a payload.
Behavioral surface
EnvironmentVarsFilesystem
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg34"scripts": {
"postinstall": "node scripts/postinstall.js"
}
High
Suspicious Lifecycle Evidence
The manifest automatically runs a postinstall script.
package.jsonView on unpkg · L34•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgskills/story-verify/examples/pytest-project/tests/test_auth.pyView file
Findings
6 High4 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPayload In Excluded Dirskills/story-verify/examples/pytest-project/tests/test_auth.py
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencescripts/postinstall.js
HighAi Review Evidencescripts/install.js
HighAi Review Evidencescripts/install.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperskills/story-verify/examples/pytest-project/tests/test_auth.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to agile-sddf@2.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing agile-sddf@2.0.3. 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.