mdast-range
Renamed to remark-range
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): mdast-range is an intentional tombstone/redirect package pointing users to remark-range. No deps, no code, and minimal metadata are expected for this type of deprecation stub. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 0 / 0 | |
| 1.0.1 | 1 / 13 | |
| 1.0.0 | 1 / 13 | |
| 0.4.3 | 1 / 13 | |
| 0.4.2 | 0 / 13 | |
| 0.4.1 | 0 / 13 | |
| 0.4.0 | 0 / 12 | |
| 0.3.0 | 0 / 12 | |
| 0.2.1 | 0 / 12 | |
| 0.2.0 | 0 / 12 | |
| 0.1.0 | 0 / 12 |
v2.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wooorm.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.