registry / @chemx/starter-kit / 26.9.12-272
@chemx/starter-kit@26.9.12-272
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no registry install lifecycle and its potentially sensitive actions are reachable through explicit CLI commands and prompts. Static inspection found no concrete malicious execution, secret theft, persistence chain, or unconsented broad agent-control mutation.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs create, init, install-hooks, or audit --share.
Impact
The selected project may receive generated files or requested hooks; supplied license or GitHub credentials are used for their requested services.
Mechanism
Explicit CLI scaffolding, guardrail setup, and GitHub discussion publishing.
AI rationale
The package has no registry install lifecycle and its potentially sensitive actions are reachable through explicit CLI commands and prompts. Static inspection found no concrete malicious execution, secret theft, persistence chain, or unconsented broad agent-control mutation.
Evidence
.cursorrules.git/hooks/pre-commit.github/workflows/chemx-audit.yml.chemx/config.json~/.chemical-x/config.json~/.chemical-x/device_id
Network endpoints2
chemicalx.xophz.com/api/starter-kit/downloadapi.github.com/graphql
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Explicit scaffold commands write fetched templates and a project .cursorrules file.
- Licensed scaffolding sends the entered license key and a generated device ID to the vendor endpoint.
- The optional sharing feature can use a GitHub token to post audit content.
- Child-process use is limited to named utilities such as open, gum, git, and clipboard tools.
- The manifest has CLI entry points but no install lifecycle hook.
Evidence against
- No preinstall, install, or postinstall script is declared.
- Agent-related file creation is part of an explicitly invoked project scaffolding command.
- GitHub publishing requires an explicit share path and prompts for post details.
- No secret harvesting, arbitrary shell execution, obfuscated payload, self-dependency, or automatic network execution was found.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
5 flagged · loading sourcecli/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 · L2cli/terminal.jsView file
10} else if (platform === "win32") {
L11: spawnSync("cmd.exe", ["/c", "start", '""', url], { stdio: "ignore" });
L12: } else {
High
cli/license.jsView file
3import os from 'node:os';
L4: import { spawnSync } from 'node:child_process';
L5: import {
...
L16:
L17: export const API_BASE = process.env.CHEMICAL_X_API_URL || 'https://chemicalx.xophz.com';
L18: export const URL_LEARN = 'https://chemicalx.xophz.com';
Findings
5 High2 Medium5 Low
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
HighPrevious Version Dangerous Deltacli/audit/social-git.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @chemx/starter-kit@26.9.12-272.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chemx/starter-kit@26.9.12-272 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.