@polyglot-bundles/rw-word-lists
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org sibling package in the polyglot-bundles monorepo; consistent with legitimate refactoring. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 35 new files match the CEFR level exports (pre-a1 through c1) added in this version; expected growth for a word-list package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 1 / 5 | |
| 0.4.1 | 2 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 3 | |
| 0.1.3 | 1 / 3 | |
| 0.1.2 | 1 / 3 | |
| 0.1.1 | 1 / 2 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.