@markdoc/markdoc
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires inside PEG.js-generated grammar parser — standard pattern for this parser toolkit, not attacker-controlled. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() appears only in test files (react.test.ts) to evaluate rendered static output — not shipped in production dist. | ai | |
| phantom-deps | phantom-dep:@types/linkify-it | AI (phantom-deps): Type-only optional dependency; not imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): Type-only optional dependency; not imported at runtime by convention. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.5.8 | 0 / 20 | |
| 0.5.7 | 2 / 20 | |
| 0.5.6 | 2 / 18 | |
| 0.5.5 | 2 / 18 | |
| 0.5.4 | 2 / 18 | |
| 0.5.3 | 2 / 18 | |
| 0.5.2 | 2 / 18 | |
| 0.5.1 | 2 / 18 | |
| 0.5.0 | 2 / 18 |
v0.5.8
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mfix-stripe) on 2026-07-15, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.