@spinajs/intl-http
Internationalization support for http module
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:@spinajs/intl | AI (phantom-deps): Same-org monorepo dep; may be used transitively or via re-export, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@spinajs/log-common | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@spinajs/reflection | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai |
Versions (showing 10 of 110)
| Version | Deps | Published |
|---|---|---|
| 2.0.372 | 7 / 1 | |
| 2.0.371 | 7 / 1 | |
| 2.0.370 | 7 / 1 | |
| 2.0.369 | 7 / 1 | |
| 2.0.368 | 7 / 1 | |
| 2.0.367 | 7 / 1 | |
| 2.0.363 | 7 / 1 | |
| 2.0.362 | 7 / 1 | |
| 2.0.361 | 7 / 1 | |
| 2.0.360 | 7 / 1 |
v2.0.372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.370
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.