@mdit/plugin-mark
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): Type-only dep used at compile time; not directly imported at runtime is expected. | ai | |
| phantom-deps | phantom-dep:@mdit/plugin-inline-rule | AI (phantom-deps): Same-org sibling dep; may be re-exported or used indirectly via bundled dist. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.23.2 | 2 / 0 | |
| 0.23.1 | 2 / 0 | |
| 0.22.2 | 1 / 0 | |
| 0.22.1 | 1 / 0 | |
| 0.22.0 | 1 / 0 | |
| 0.21.0 | 1 / 0 | |
| 0.20.0 | 1 / 0 | |
| 0.19.0 | 1 / 0 |
v0.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.