@dev-mainsequence/command-center-sdk@0.5.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-aiThe automatic lifecycle combines an unrestricted environment-selected destination with forwarding of an existing access token. This establishes conditional credential exposure, not proven malware intent or a confirmed covert attack.
Decision evidence
public snapshot- The package declares an automatic postinstall entrypoint.
- Postinstall copies agent skills and, when environment configuration is present, fetches an MCP catalog.
- The MCP URL is taken from environment configuration without a destination allowlist, while the access token is taken from MAINSEQUENCE_ACCESS_TOKEN.
- The MCP client sends that token as a Bearer authorization header to the configured URL.
- Fetched MCP skill content is written into the consumer repository's agent-skills directory.
- The MCP synchronization is skipped when its URL or token is absent and errors do not block installation.
- The code validates paths and uses a dedicated agent-skill namespace.
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.5.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.5.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.