i18next-xhr-backend
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jamuhl
Keywords
i18nexti18next-backend
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:istanbul | AI (npm-metadata): Dev-only dependency used for test coverage; does not affect runtime consumers. | ai | |
| npm-metadata | url-dep:karma-coverage | AI (npm-metadata): Dev-only dependency used for test coverage reporting; does not affect runtime consumers. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 1 / 39 |
v3.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.