@bfrs/agentic-components@0.8.7
Shiprocket agentic component library and documentation showcase.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package automatically mutates foreign agent instruction files and consumer build configuration during postinstall, without affirmative consent. This is an unconsented agent control-surface change and warrants blocking publication.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package with lifecycle scripts enabled and without the skip environment variable.
Impact
Project agents receive package-provided context through their instruction files, and consumer builds are altered to run the package’s lint tool.
Mechanism
The hook copies its context file, adds a reference to AGENTS.md or CLAUDE.md, and inserts a lint command into the consumer’s package scripts and build commands.
Policy narrative
On installation, the package’s postinstall hook copies its context document into the consumer project, modifies agent instruction files to reference it, and changes build scripts to run its lint command. The hook’s environment variable provides an opt-out, but the default install performs these agent configuration and project script changes automatically.
AI rationale
The package automatically mutates foreign agent instruction files and consumer build configuration during postinstall, without affirmative consent. This is an unconsented agent control-surface change and warrants blocking publication.
Evidence
package.jsonscripts/postinstall.cjsAGENTS.mdCLAUDE.mdBFRS_AGENTIC_COMPONENTS.md
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- The manifest runs scripts/postinstall.cjs automatically on install.
- The hook proceeds in a consumer lifecycle and copies package context into the consumer project.
- It creates or appends references in AGENTS.md and CLAUDE.md, which are agent instruction files.
- The hook also adds a lint command and rewrites consumer build scripts to run that command.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg55"postinstall": "node scripts/postinstall.cjs",
"dev": "vite --host 0.0.0.0",
"build": "npm run build:lib && npm run build:custom-elements && npm run build:demo",
"build
High
Suspicious Lifecycle Evidence
The manifest runs scripts/postinstall.cjs automatically on install.
package.jsonView on unpkg · L55•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/postinstall.cjsView file
Findings
1 Critical4 High3 Medium4 Low
CriticalAi Agent Control Hijackscripts/postinstall.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/fonts.css
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencescripts/postinstall.cjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @bfrs/agentic-components@0.8.7.
See all versions of @bfrs/agentic-components for other recorded verdicts.
- Avoid installing @bfrs/agentic-components@0.8.7. 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.