registry / @chem-x/starter-kit / 26.9.13-632
@chem-x/starter-kit@26.9.13-632
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected process, network, and project-file behaviors are part of explicitly invoked CLI workflows. No concrete attack behavior was established.
Static reason
No blocking static signals were detected.
Trigger
The user invokes the CLI and selects an audit, share, or scaffolding action.
Impact
No malicious or unconsented effect was established from the inspected source.
Mechanism
The package verifies a supplied license with its configured service, publishes audit details only through the share flow, and writes scaffold files in a requested project directory.
AI rationale
The manifest has no install hook, and inspected process, network, and project-file behaviors are part of explicitly invoked CLI workflows. No concrete attack behavior was established.
Evidence
~/.chemical-x/config.json~/.chemical-x/device_idrequested project directory
Network endpoints3
chemicalx.xophz.commycompassconsulting.comgithub.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes an explicitly invoked CLI and has no install lifecycle hook.
- Discussion posting is an interactive user-selected action; the CLI collects project details before publishing.
- Browser launching passes a URL as an argument to the platform browser opener, without shell command interpolation.
- License verification sends the entered license key and generated device ID to the configured Chemical X service.
- Scaffolding writes selected blueprint files under the requested project directory, after checking that it is empty.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
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 {
...
L17:
L18: export const API_BASE = process.env.CHEMICAL_X_API_URL || 'https://chemicalx.xophz.com';
L19: export const GATEKEEPER_API_URL = process.env.COMPASS_GATEKEEPER_URL || 'https://mycompassconsulting.com/wp-json/compass/v1/gatekeeper';
Findings
4 High2 Medium6 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
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @chem-x/starter-kit@26.9.13-632.
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.13-632 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.