@chem-x/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 agent configuration capability warrants a warning because it changes agent guidance and editor configuration, but the inspected operations require an explicit installer selection. The declared postinstall target is absent, and no concrete malicious behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the installer and selects the agent query or MCP setup option.
Impact
These changes affect later agent behavior and configuration, but the inspected code presents them as user-invoked setup.
Mechanism
The query installer may append guidance to AGENTS.md; MCP setup merges a Chemical X server entry into editor configuration.
AI rationale
The agent configuration capability warrants a warning because it changes agent guidance and editor configuration, but the inspected operations require an explicit installer selection. The declared postinstall target is absent, and no concrete malicious behavior was established.
Evidence
cli/installer.jscli/mcp/installer.jsAGENTS.md.cursor/mcp.json.vscode/mcp.jsonpackage.json
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package manifest declares a postinstall command that points to a file absent from the package snapshot.
- The installer can append a rule directing AI agents to use the package’s query command before broad searches.
- The installer offers agent-query setup as an explicit interactive choice and runs it only after that choice.
- MCP setup adds a Chemical X server entry to project editor configuration when invoked.
- The MCP installer spec confirms the project configuration entry is created by the installer.
Evidence against
- The agent configuration changes are exposed through an interactive installer choice, rather than code shown running during package installation.
- The MCP setup writes a named Chemical X server configuration and preserves existing configuration through a merge.
- The manifest’s postinstall target is absent from the inspected package file list, so its behavior is not present in this snapshot.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
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 @chem-x/starter-kit@26.9.16-41.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chem-x/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.