@modern-js/babel-plugin-module-resolver
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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): Standard modern.js monorepo README; link-dump heuristic is a stable FP for these sub-packages. | ai |
Versions (showing 51 of 101)
| Version | Deps | Published |
|---|---|---|
| 2.71.1 | 5 / 8 | |
| 2.71.0 | 5 / 8 | |
| 2.70.8 | 5 / 8 | |
| 2.70.7 | 5 / 8 | |
| 2.70.6 | 5 / 8 | |
| 2.70.5 | 5 / 8 | |
| 2.70.4 | 5 / 8 | |
| 2.70.3 | 5 / 8 | |
| 2.70.2 | 5 / 8 | |
| 2.70.1 | 5 / 8 | |
| 2.70.0 | 5 / 8 | |
| 2.69.7 | 5 / 8 | |
| 2.69.6 | 5 / 8 | |
| 2.69.5 | 5 / 8 | |
| 2.69.4 | 5 / 8 | |
| 2.69.3 | 5 / 8 | |
| 2.69.2 | 5 / 8 | |
| 2.69.1 | 5 / 8 | |
| 2.69.0 | 5 / 8 | |
| 2.68.20 | 5 / 8 | |
| 2.68.19 | 5 / 8 | |
| 2.68.18 | 5 / 8 | |
| 2.68.17 | 5 / 8 | |
| 2.68.16 | 5 / 8 | |
| 2.68.15 | 5 / 8 | |
| 2.68.14 | 5 / 8 | |
| 2.68.13 | 5 / 8 | |
| 2.68.12 | 5 / 8 | |
| 2.68.11 | 5 / 8 | |
| 2.68.10 | 5 / 8 | |
| 2.68.9 | 5 / 8 | |
| 2.68.8 | 5 / 8 | |
| 2.68.7 | 5 / 8 | |
| 2.68.6 | 5 / 8 | |
| 2.68.5 | 5 / 8 | |
| 2.68.4 | 5 / 8 | |
| 2.68.3 | 5 / 8 | |
| 2.68.2 | 5 / 8 | |
| 2.68.1 | 5 / 8 | |
| 2.68.0 | 5 / 8 | |
| 2.67.11 | 5 / 8 | |
| 2.67.10 | 5 / 8 | |
| 2.67.9 | 5 / 8 | |
| 2.67.8 | 5 / 8 | |
| 2.67.7 | 5 / 8 | |
| 2.67.6 | 5 / 8 | |
| 2.67.5 | 5 / 8 | |
| 2.67.4 | 5 / 8 | |
| 2.67.3 | 5 / 8 | |
| 2.67.2 | 5 / 8 | |
| 2.67.1 | 5 / 8 |
v2.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.67.3
1 findingThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.
v2.67.2
1 findingThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.
v2.67.1
1 findingThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.