@panneau/intl
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:lodash-es | AI (phantom-deps): Build-script dependency declared in package.json; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai | |
| phantom-deps | phantom-dep:gettext-parser | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai | |
| phantom-deps | phantom-dep:@formatjs/cli-lib | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Used in build scripts, not direct imports; stable pattern for this intl tooling package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 9 / 2 | |
| 4.0.50 | 9 / 2 | |
| 4.0.48 | 9 / 2 | |
| 4.0.45 | 9 / 2 | |
| 4.0.41 | 9 / 2 | |
| 4.0.38 | 9 / 2 | |
| 4.0.37 | 9 / 2 | |
| 4.0.36 | 9 / 2 | |
| 4.0.27 | 9 / 2 | |
| 4.0.26 | 9 / 2 | |
| 4.0.24 | 9 / 2 | |
| 4.0.21 | 9 / 2 | |
| 4.0.18 | 9 / 2 | |
| 4.0.17 | 9 / 2 | |
| 4.0.8 | 10 / 2 | |
| 4.0.7 | 10 / 2 | |
| 4.0.6 | 10 / 2 | |
| 4.0.5 | 10 / 2 | |
| 4.0.4 | 10 / 2 | |
| 4.0.3 | 10 / 2 | |
| 4.0.2 | 10 / 2 | |
| 4.0.1 | 10 / 2 | |
| 4.0.0 | 10 / 2 | |
| 3.0.323 | 10 / 2 | |
| 3.0.322 | 10 / 2 | |
| 3.0.321 | 10 / 2 | |
| 3.0.314 | 10 / 2 | |
| 3.0.307 | 10 / 2 |
v4.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.323
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.322
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.321
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.