respecpow@0.9.2
Spec-Powered AI Development Framework - 融合 OpenSpec 规范驱动 + Superpowers 执行引擎的企业级 AI 辅助编程框架（安装即生效版）
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest automatically runs a postinstall script that writes behavior-bearing command hooks into global agent settings without consent. This meets the block policy for unconsented install-time mutation of an AI-agent control surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package when a Claude Code or CodeBuddy settings directory exists.
Impact
The package changes agent control settings so its commands run automatically on configured events.
Mechanism
The postinstall script reads existing settings, appends hooks if matching commands are absent, and writes the settings file without a consent check.
Policy narrative
The package’s install hook edits global Claude Code and CodeBuddy settings and registers commands to run on session and tool events. The mutation happens during npm postinstall without a consent prompt, creating an unconsented AI-agent control surface.
AI rationale
The manifest automatically runs a postinstall script that writes behavior-bearing command hooks into global agent settings without consent. This meets the block policy for unconsented install-time mutation of an AI-agent control surface.
Evidence
package.jsonscripts/postinstall.js~/.claude/settings.json~/.codebuddy/settings.json
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 package manifest runs scripts/postinstall.js automatically during installation.
- The postinstall code adds commands to global Claude Code and CodeBuddy hooks when those tools’ settings directories exist; it does not request consent.
- The added hooks run SpecPow commands on session start, prompt submission, and before and after tool use, and the script writes the modified settings files.
- Separate CLI init and update paths handle project-level artifacts, while the postinstall path directly registers global hooks.
Evidence against
- The hooks invoke this package’s own hook-run commands; inspected source does not establish credential theft or a remote payload.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js || echo 'Postinstall skipped'
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js || echo 'Postinstall skipped'
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/core/init/codegraph-step.jsView file
11*/
L12: import { execSync } from 'child_process';
L13: // ============================================================
High
Child Process
Package source references child process execution.
dist/core/init/codegraph-step.jsView on unpkg · L11Findings
1 Critical6 High3 Medium5 Low
CriticalAi Agent Control Hijackscripts/postinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/core/init/codegraph-step.js
HighShell
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/core/init/engine.js
HighRuntime Package Installdist/core/init/codegraph-step.js
HighSemantic Analysis Limiteddist/core/init/engine.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Low
Affected versions and remediation
This report applies to respecpow@0.9.2.
See all versions of respecpow for other recorded verdicts.
- Avoid installing respecpow@0.9.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.