@marimo-team/codemirror-mcp
5
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
akshaykamscolnick
Keywords
codemirrorcodemirror-pluginmcp
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD publishing; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration; SLSA attestation confirms legitimate publish pipeline. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 0 / 15 | |
| 0.1.5 | 0 / 15 | |
| 0.1.4 | 0 / 15 | |
| 0.1.3 | 0 / 15 | |
| 0.1.2 | 0 / 15 |
v0.1.7
2 findings
HIGH
Publisher changed: mscolnick → GitHub Actions (on 2026-07-02)
provenance
This version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.