registry / AI-agent control-surface risk / @rfdtech/components
@rfdtech/components
Shared React component library for Clet projects
This report shows the evidence for @rfdtech/components@2.5.0. 7 of 9 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe package performs unconsented AI-agent configuration and instruction-file writes through an install lifecycle hook. This meets the blocking policy for automatic lifecycle mutation of a broad AI-agent control surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package with its postinstall hook enabled and without setting RFDUI_SKIP_SETUP.
Impact
Installation can change files that influence later AI-agent behavior and register this package’s MCP server without a separate setup command.
Mechanism
The hook launches the setup CLI. Setup writes shared .ai guidance unconditionally and adds package guidance or MCP configuration for detected tools.
Policy narrative
During package installation, the postinstall hook launches the setup CLI unless an opt-out variable is set. Setup always writes cross-tool guidance into the consumer project’s .ai directory. When tool markers are present, it also adds project configuration and agent instructions; Codex setup can append a server entry to the user-level configuration. These changes happen as part of installation without a separate user-invoked setup command.
AI rationale
The package performs unconsented AI-agent configuration and instruction-file writes through an install lifecycle hook. This meets the blocking policy for automatic lifecycle mutation of a broad AI-agent control surface.
Evidence
package.jsonscripts/postinstall.mjsdist/mcp/cli.jsdist/mcp/installers/setup.jsdist/mcp/installers/claude.jsdist/mcp/installers/opencode.jsdist/mcp/installers/codex.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 96.0% confidence with low false-positive risk.
Evidence for policy risk
- The package postinstall launches its setup CLI during installation, with an environment variable to skip setup.
- Setup unconditionally writes cross-tool instructions into the consumer project’s .ai directory.
- Detected tools also receive configuration or instruction-file changes; Codex setup can write to the user-level configuration file.
- The CLI routes the setup command to the installer that performs these writes.
Evidence against
- Tool-specific setup is conditional on detecting existing tool markers, and the postinstall supports an opt-out variable.
- The installer adds a package-specific MCP server entry and setup guidance.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/next.cjsView file
1Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./next-DoxSCyS0.cjs");exports.ACCESSIBILITY_DEFAULTS=e.ji,exports.ACCESSIBILITY_STORAGE_KEY=e.Mi...
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/next.cjsView on unpkg · L1Findings
2 High6 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/components.css
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/next.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdist/mcp/skill/antislop-human/contrast-check.py
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @rfdtech/components@2.5.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @rfdtech/components@2.5.0. 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.
Versions
9 known versions2.5.0latestshownMaliciousSoft block: AI-agent control surfaceBlockPublishedOct 10, 2026, 4:03 PM2.4.7MaliciousSoft block: AI-agent control surfaceBlockPublishedOct 8, 2026, 10:20 PM2.4.3MaliciousSoft block: AI-agent control surfaceBlockPublishedOct 3, 2026, 1:48 AM2.4.2MaliciousSoft block: AI-agent control surfaceBlockPublished