@polyglot-bundles/uz-af-minimal-pairs
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@polyglot-bundles/content-shared | AI (phantom-deps): Same-org sibling dep; declared in package.json dependencies, phantom-dep heuristic false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped data package in a monorepo; missing description is a style issue, not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@polyglot-bundles/uz-minimal-pairs | AI (phantom-deps): Sibling package in same org scope; declared as runtime dep, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 0 / 5 | |
| 0.5.0 | 0 / 5 | |
| 0.4.0 | 0 / 5 | |
| 0.3.1 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.5 | 0 / 5 | |
| 0.2.4 | 2 / 3 | |
| 0.2.3 | 2 / 3 | |
| 0.2.2 | 2 / 2 | |
| 0.2.1 | 2 / 2 | |
| 0.2.0 | 2 / 2 |
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.