@dev-mainsequence/command-center-sdk@0.5.2
The framework-neutral SDK for building Command Center-compatible resource applications, navigation, layouts, themes, feedback, and embeds.
AI Security Review
scanned 29d ago · by lpm-firewall-aiPostinstall always installs this package's own skills under .agents/skills/command-center and, unless opted out, forwards MAINSEQUENCE_ACCESS_TOKEN to an operator-chosen HTTP(S) MCP URL before writing returned skills under .agents/skills/mainsequence. That is first-party agent-extension setup with conditional credential exposure, not a hardcoded foreign control-surface hijack.
Decision evidence
public snapshot- package.json postinstall runs node ./cli/postinstall.mjs on install.
- Local postinstall calls installAgentSkills with command npm postinstall and copies skills into the consumer project.
- The skill destination is .agents/skills/command-center, and entries in that namespace that are not in the packaged set are removed.
- Unless COMMAND_CENTER_SDK_MCP_POSTINSTALL is 0, a present MAINSEQUENCE_ACCESS_TOKEN is sent as a bearer token to any operator HTTP(S) MCP URL, and returned skills are written under .agents/skills/mainsequence.
- There is no preinstall hook, no runtime dependency on this package name, and dist/index.js only re-exports resource modules.
- The MCP URL is taken from the environment, sync is skipped when the URL or token is missing, and fetch errors do not fail the install.
- Skill copies stay inside the command-center and mainsequence namespaces and reject symbolic links and parent-directory paths.
- child_process helpers live in CLI maintenance modules and are not called by postinstall.
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.2.
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.2 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.