markdown-it-anchor
Header anchors for markdown-it.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/markdownItAnchor.modern.mjs | AI (source-diff): Minified ESM bundle of markdown-it-anchor plugin; readable logic matches expected functionality. Standard build output, not obfuscation. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 9.2.0 | 0 / 7 | |
| 9.1.0 | 0 / 7 | |
| 9.0.2 | 0 / 6 | |
| 9.0.1 | 0 / 6 | |
| 9.0.0 | 0 / 6 | |
| 8.6.7 | 0 / 6 | |
| 8.6.6 | 0 / 6 | |
| 8.6.5 | 0 / 6 | |
| 8.6.4 | 0 / 6 | |
| 8.6.3 | 0 / 6 | |
| 8.6.2 | 0 / 6 | |
| 8.6.1 | 0 / 6 | |
| 8.6.0 | 0 / 6 | |
| 8.5.0 | 0 / 6 | |
| 8.4.1 | 0 / 6 | |
| 8.4.0 | 0 / 6 | |
| 8.3.1 | 0 / 6 | |
| 8.3.0 | 0 / 6 | |
| 8.2.0 | 0 / 6 | |
| 8.1.3 | 0 / 5 | |
| 8.1.2 | 0 / 5 | |
| 8.1.1 | 0 / 5 | |
| 8.1.0 | 0 / 5 | |
| 8.0.5 | 0 / 5 | |
| 8.0.4 | 0 / 5 | |
| 8.0.3 | 0 / 5 | |
| 8.0.2 | 0 / 5 | |
| 8.0.1 | 0 / 5 | |
| 8.0.0 | 0 / 5 | |
| 7.1.0 | 0 / 4 | |
| 7.0.2 | 0 / 4 | |
| 7.0.1 | 0 / 4 | |
| 7.0.0 | 0 / 4 | |
| 6.0.1 | 0 / 4 | |
| 6.0.0 | 0 / 4 | |
| 5.3.0 | 0 / 4 | |
| 5.2.7 | 0 / 4 | |
| 5.2.5 | 0 / 4 | |
| 5.2.4 | 0 / 4 | |
| 5.2.3 | 0 / 4 | |
| 5.2.2 | 0 / 4 | |
| 5.2.1 | 0 / 4 | |
| 5.2.0 | 0 / 4 | |
| 5.1.0 | 0 / 3 | |
| 5.0.2 | 0 / 3 | |
| 5.0.1 | 0 / 3 | |
| 5.0.0 | 0 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.0.0 | 1 / 8 | |
| 2.7.1 | 1 / 7 | |
| 2.7.0 | 1 / 8 |
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.