copilot-framework@1.6.0
Contract-first Copilot scaffolding and workspace bootstrap scripts for Edenred repositories.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection confirms that an npm postinstall hook automatically changes repository-level Copilot configuration when it detects a repository, without an interactive consent step. The setup is first-party and local, so this supports a warning for agent extension lifecycle risk rather than a block.
Decision evidence
public snapshot- package.json runs a postinstall hook that starts scripts/postinstall.js.
- The hook skips development, CI, and production installs; in other repository installs it proceeds without an interactive consent step.
- In a detected repository, the hook copies Copilot workspace assets and creates an MCP configuration.
- The MCP configuration is merged with existing settings and written to the repository.
- The generated entry registers this package's local MCP server, making the behavior first-party setup.
- The inspected setup uses a local Node command and preserves existing MCP servers in its merge.
- No credential transfer or remote endpoint was identified in the inspected postinstall path.
Source & flagged code
9 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 copilot-framework@1.6.0.
See all versions of copilot-framework for other recorded verdicts.
- Review the evidence and your use of copilot-framework@1.6.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.