@formatjs/intl-pluralrules
Polyfill for Intl.PluralRules
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/es-abstract | AI (dependencies): @types/es-abstract is a TypeScript type definition package for es-abstract, a legitimate runtime dep. Its presence as a dep in this formatjs polyfill is a known pattern, not a risk. | ai | |
| source-diff | large-new-source-files | AI (source-diff): FormatJS polyfill packages ship per-locale data files; large file count increases are expected as locale coverage expands and are not indicative of injected code. | ai | |
| phantom-deps | phantom-dep:@formatjs/intl-getcanonicallocales | AI (phantom-deps): Same-org sibling dependency declared in package.json; phantom-dep flag is a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@formatjs/intl-getcanonicallocales | AI (dependencies): Sibling package in the same @formatjs org scope, maintained by the same publisher (longlho). No risk generalizes across versions. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption on npm; no provenance is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper, declared as a dependency, and a known implicit dependency for TypeScript-compiled packages. Stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): formatjs monorepo migrated to GitHub Actions CI/CD publishing with SLSA provenance attestation. This is a legitimate, documented transition for this package family — stronger integrity than personal account publishing. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: @formatjs/intl-pluralrules is a long-established package (2424 days, 182 versions) in the FormatJS monorepo. Inflated semver signal is incorrect for this package. | ai |
Versions (showing 51 of 186)
| Version | Deps | Published |
|---|---|---|
| 6.3.9 | 2 / 2 | |
| 6.3.8 | 2 / 2 | |
| 6.3.7 | 2 / 2 | |
| 6.3.6 | 2 / 2 | |
| 6.3.5 | 2 / 2 | |
| 6.3.4 | 2 / 2 | |
| 6.3.3 | 2 / 2 | |
| 6.3.2 | 2 / 2 | |
| 6.3.1 | 3 / 2 | |
| 6.2.4 | 3 / 2 | |
| 6.2.3 | 4 / 2 | |
| 6.2.2 | 4 / 2 | |
| 6.2.1 | 4 / 2 | |
| 6.2.0 | 4 / 2 | |
| 6.1.2 | 4 / 2 | |
| 6.1.1 | 4 / 2 | |
| 6.1.0 | 4 / 2 | |
| 6.0.6 | 4 / 2 | |
| 6.0.5 | 4 / 2 | |
| 6.0.4 | 4 / 2 | |
| 6.0.2 | 4 / 2 | |
| 6.0.1 | 4 / 2 | |
| 6.0.0 | 4 / 2 | |
| 5.4.6 | 4 / 2 | |
| 5.4.5 | 4 / 2 | |
| 5.4.4 | 4 / 2 | |
| 5.4.3 | 4 / 2 | |
| 5.4.2 | 4 / 2 | |
| 5.4.1 | 4 / 2 | |
| 5.4.0 | 4 / 2 | |
| 5.3.6 | 3 / 2 | |
| 5.3.5 | 3 / 2 | |
| 5.3.4 | 3 / 2 | |
| 5.3.3 | 3 / 2 | |
| 5.3.2 | 3 / 2 | |
| 5.3.1 | 3 / 2 | |
| 5.3.0 | 3 / 2 | |
| 5.2.17 | 3 / 2 | |
| 5.2.16 | 3 / 2 | |
| 5.2.15 | 3 / 2 | |
| 5.2.14 | 3 / 2 | |
| 5.2.13 | 3 / 2 | |
| 5.2.12 | 3 / 2 | |
| 5.2.11 | 3 / 2 | |
| 5.2.10 | 3 / 2 | |
| 5.2.9 | 3 / 2 | |
| 5.2.8 | 3 / 2 | |
| 5.2.7 | 3 / 2 | |
| 5.2.6 | 3 / 2 | |
| 5.2.5 | 3 / 2 | |
| 5.2.4 | 3 / 2 |
v6.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-12. This could indicate a legitimate maintainer transition or an account compromise.