@hpcc-js/markdown-it-plugins
markdown-it plugins
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@observablehq/runtime | AI (dependencies): Well-known Observable HQ runtime; stable legitimate dependency for this markdown plugin package. | ai | |
| dependencies | unvetted-dep:@observablehq/framework | AI (dependencies): Well-known Observable HQ framework; stable legitimate dependency for this markdown plugin package. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): Type-only package; not imported at runtime by design, stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 5 / 5 | |
| 1.6.1 | 5 / 5 | |
| 1.6.0 | 5 / 5 | |
| 1.5.15 | 5 / 5 | |
| 1.5.14 | 4 / 5 | |
| 1.5.13 | 4 / 5 | |
| 1.5.12 | 4 / 5 | |
| 1.5.11 | 4 / 5 | |
| 1.5.10 | 4 / 5 | |
| 1.5.8 | 4 / 5 | |
| 1.5.7 | 4 / 5 | |
| 1.5.6 | 4 / 5 | |
| 1.5.5 | 4 / 5 | |
| 1.5.4 | 4 / 5 | |
| 1.5.3 | 4 / 5 | |
| 1.5.2 | 4 / 5 | |
| 1.5.1 | 4 / 5 | |
| 1.5.0 | 4 / 5 | |
| 1.4.7 | 4 / 5 | |
| 1.4.6 | 4 / 5 | |
| 1.4.5 | 4 / 5 | |
| 1.4.4 | 4 / 5 | |
| 1.4.3 | 4 / 5 | |
| 1.4.2 | 4 / 5 | |
| 1.4.1 | 4 / 5 | |
| 1.4.0 | 4 / 5 | |
| 1.3.10 | 4 / 5 | |
| 1.3.9 | 4 / 5 | |
| 1.3.8 | 4 / 5 | |
| 1.3.6 | 4 / 5 | |
| 1.3.5 | 4 / 5 | |
| 1.3.2 | 3 / 9 |
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.