sdd-flow-kit
Cross-agent SDD automated development workflow kit with PRD layered architecture, task splitting, context compression, and pending confirmations.
This report shows the evidence for sdd-flow-kit@1.8.2. 11 of 23 known versions are blocked or flagged. The newest version, 1.10.1, is allowed. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic lifecycle hook performs broad, unconsented mutation of consumer AI-agent control surfaces and adds command permissions. This meets the install-hook abuse blocking policy.
Decision evidence
public snapshot- The package runs a postinstall script automatically.
- Postinstall resolves the consumer project and calls setup with confirmation forced on.
- Setup writes skills into Cursor, Claude Code, Codex, and OpenClaw project control directories.
- Setup grants Claude Code broad npm, npx, pnpm, node, file-operation permissions without consent.
- The postinstall invokes setup for the resolved project with confirmation enabled and dry-run disabled.
- Setup targets Cursor, Claude Code, Codex, and OpenClaw skill directories.
- Claude Code permissions include npm, npx, pnpm, node, and file-operation commands.
- No network endpoint or credential exfiltration was found in the inspected lifecycle path.
- The observed writes are local project changes rather than a remote payload download.
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 unpkgPackage source references child process execution.
dist/core/agentRemediateInvoke.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to sdd-flow-kit@1.8.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing sdd-flow-kit@1.8.2. 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.