@chemx/starter-kit@26.9.16-41
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source shows explicit-user-command agent configuration changes, which warrant a warning under the agent integration policy. The declared postinstall target is missing, but no source evidence establishes what it would do or a malicious chain.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the installer wizard and selects query setup, or explicitly invokes the MCP setup command.
Impact
Project AI agents may be steered to use the package’s search workflow, and configured clients may launch its MCP server.
Mechanism
The query setup appends search workflow instructions to an existing AGENTS.md file; MCP setup adds a Chemical X server entry to project configuration.
AI rationale
The source shows explicit-user-command agent configuration changes, which warrant a warning under the agent integration policy. The declared postinstall target is missing, but no source evidence establishes what it would do or a malicious chain.
Evidence
cli/installer.jscli/mcp/installer.jspackage.jsoncli/mcp/installer.spec.js
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package declares a postinstall command, but its referenced scripts/postinstall.mjs file is absent from the package snapshot.
- The installer wizard offers a user-selected query setup that can append instructions to an existing AGENTS.md file.
- The added AGENTS.md instructions direct AI agents to use the package’s search command before broad searches and file dumps.
- The MCP installer writes a Chemical X server entry into project Cursor configuration when explicitly invoked.
- A test confirms the project MCP installer creates Cursor MCP configuration.
Evidence against
- The AGENTS.md mutation is part of a selectable installer wizard, not an automatic install hook.
- The MCP installer is reached through explicit install-mcp or setup-mcp CLI commands.
- The inspected excerpts show no credential collection or outbound credential transmission.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
Source & flagged code
6 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 unpkgcli/navigator-share.jsView file
2import path from 'node:path';
L3: import { spawnSync } from 'node:child_process';
L4: import {
High
Child Process
Package source references child process execution.
cli/navigator-share.jsView on unpkg · L2Findings
5 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli/navigator-share.js
HighShellcli/terminal.js
HighSame File Env Network Executioncli/license.js
HighTrigger Reachable External Ai Agent Control Surface Mutationcli/scaffold.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @chemx/starter-kit@26.9.16-41.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chemx/starter-kit@26.9.16-41 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.