@zseven-w/pen-mcp
MCP server, document manager, and tools for OpenPencil
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP references are in security test files testing localhost/loopback behavior — not production code or exfiltration. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic fires due to config-only reference, not a real missing import. | ai | |
| phantom-deps | phantom-dep:@iconify-json/lucide | AI (phantom-deps): Icon data packages are typically referenced via config/tooling, not direct imports. | ai | |
| phantom-deps | phantom-dep:@iconify-json/feather | AI (phantom-deps): Icon data packages are typically referenced via config/tooling, not direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.6 | 8 / 1 | |
| 0.7.5 | 8 / 1 | |
| 0.7.4 | 8 / 1 | |
| 0.7.3 | 8 / 1 | |
| 0.7.2 | 8 / 1 | |
| 0.7.1 | 8 / 1 | |
| 0.7.0 | 8 / 1 |
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.