@dev-mainsequence/command-center-sdk@0.3.0
The framework-neutral SDK for building Command Center-compatible resource applications, navigation, layouts, themes, feedback, and embeds.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not concrete malware: there is no self-dependency, secret harvesting, stealthy payload, or broad overwrite. It is a real first-party agent-extension lifecycle risk because installation automatically provisions local and conditionally remote skills.
Decision evidence
public snapshot- The npm postinstall hook automatically installs agent skills into the consumer repository.
- When configured environment credentials exist, postinstall sends the access token to an MCP URL and installs returned skill content.
- Remote MCP content is written into a generic project agent-skills control surface.
- The local skills are limited to the package's command-center namespace.
- MCP installation is conditional on an existing URL and access token, validates paths and content, and uses a separate namespace.
- No self-dependency, credential harvesting, destructive lifecycle action, or hidden payload execution was found.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @dev-mainsequence/command-center-sdk@0.3.0.
See all versions of @dev-mainsequence/command-center-sdk for other recorded verdicts.
- Review the evidence and your use of @dev-mainsequence/command-center-sdk@0.3.0 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.