typedoc-plugin-markdown
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD; SLSA provenance confirms legitimate pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 269 versions over 9 years; dormancy metric is spurious for this actively maintained package. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance; absence is expected for its age. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.12.0 | 0 / 0 | |
| 4.11.0 | 0 / 0 | |
| 4.10.0 | 0 / 0 | |
| 4.9.0 | 0 / 0 | |
| 4.8.1 | 0 / 0 | |
| 4.8.0 | 0 / 0 | |
| 4.7.1 | 0 / 0 | |
| 4.7.0 | 0 / 0 | |
| 4.6.4 | 0 / 0 | |
| 3.17.1 | 1 / 0 |
v4.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.