registry / AI-agent control-surface risk / @dev-mainsequence/command-center-sdk
@dev-mainsequence/command-center-sdk
The framework-neutral SDK for building Command Center-compatible resource applications, navigation, layouts, themes, feedback, and embeds.
This report shows the evidence for @dev-mainsequence/command-center-sdk@0.4.1. 5 of 26 known versions are blocked or flagged. The newest version, 0.5.18, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package performs automatic postinstall AI-agent configuration rather than requiring an explicit user command. This meets the install-control-surface blocking policy.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall during package installation.
Impact
A dependency installation can alter an AI-agent control surface and introduce remotely sourced agent instructions without an explicit setup command.
Mechanism
The lifecycle script copies packaged skills into .agents/skills/command-center and conditionally obtains an MCP catalog using environment-provided endpoint and token values.
Policy narrative
The postinstall hook automatically writes agent skills into the consuming project's .agents control surface. It additionally activates a remote MCP skill synchronization path when endpoint and token environment variables are present, installing returned skills as part of dependency installation. This is unconsented lifecycle mutation of a broad AI-agent control surface.
AI rationale
The package performs automatic postinstall AI-agent configuration rather than requiring an explicit user command. This meets the install-control-surface blocking policy.
Evidence
package.jsoncli/postinstall.mjscli/install-agent-skills.mjs.agents/skills/command-center
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- The package automatically runs a postinstall script.
- Postinstall installs package-supplied skills into the consumer repository.
- The installer targets the broad .agents skills control surface.
- When environment configuration exists, postinstall fetches a remote MCP catalog and installs its skills.
Evidence against
- The remote MCP request requires both a configured URL and access token.
- No self-dependency is declared.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node ./cli/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./cli/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgcli/install-agent-skills.mjsView file
1Install-time code directly mutates a foreign AI-agent control surface:
L377: resolvedProjectDir,
L378: ".agents",
L379: "skills",
...
L428: const skillsParent = dirname(destinationRoot);
L429: await mkdir(skillsParent, { recursive: true });
L430: const stageRoot = await mkdtemp(join(skillsParent, ".command-center-stage-"));
...
L439: const staged = join(stageRoot, ...item.relativePath.split("/"));
L440: await mkdir(dirname(staged), { recursive: true });
L441: await cp(item.source, staged, {
L442: recursive: true,
...
L448:
L449: await mkdir(destinationRoot, { recursive: true });
Write operation from cli/install-agent-skills.mjs:
L377: resolvedProjectDir,
L378: ".agents",
L379: "skills",
...
L428: const skillsParent = dirname(destinationRoot);
L429: await mkdir(skillsParent, { recursive: t
Findings
1 Critical6 High3 Medium4 Low
CriticalAi Agent Control Hijackcli/install-agent-skills.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedstyles.css
HighKnown Malware Source Similaritycli/application-sdk-maintenance.mjs
HighKnown Malware Source Similaritycli/code-repository-sync-local-ops.mjs
HighKnown Malware Source Similaritydist/embed/static-site.js
HighKnown Malware Source Fingerprint Signaturecli/application-sdk-maintenance.mjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @dev-mainsequence/command-center-sdk@0.4.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dev-mainsequence/command-center-sdk@0.4.1. 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.