@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 86 of 186)
| Version | Deps | Published |
|---|---|---|
| 4.0.8 | 2 / 0 | |
| 4.0.7 | 2 / 0 | |
| 4.0.6 | 2 / 0 | |
| 4.0.5 | 2 / 0 | |
| 4.0.4 | 2 / 0 | |
| 4.0.3 | 2 / 0 | |
| 4.0.2 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.5.6 | 2 / 0 | |
| 3.5.5 | 2 / 0 | |
| 3.5.4 | 2 / 0 | |
| 3.5.3 | 2 / 0 | |
| 3.5.2 | 2 / 0 | |
| 3.5.1 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.4.10 | 2 / 0 | |
| 3.4.9 | 2 / 0 | |
| 3.4.8 | 2 / 0 | |
| 3.4.7 | 1 / 0 | |
| 3.4.6 | 1 / 0 | |
| 3.4.5 | 1 / 0 | |
| 3.4.4 | 1 / 0 | |
| 3.4.3 | 4 / 0 | |
| 3.4.2 | 4 / 0 | |
| 3.4.1 | 4 / 0 | |
| 3.4.0 | 2 / 0 | |
| 3.3.2 | 2 / 0 | |
| 3.3.1 | 2 / 0 | |
| 3.3.0 | 2 / 0 | |
| 3.2.5 | 2 / 0 | |
| 3.2.4 | 2 / 0 | |
| 3.2.3 | 2 / 0 | |
| 3.2.2 | 2 / 0 | |
| 3.2.1 | 2 / 0 | |
| 3.2.0 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.2 | 1 / 7 | |
| 3.0.1 | 1 / 7 | |
| 3.0.0 | 1 / 7 | |
| 2.2.11 | 1 / 7 | |
| 2.2.10 | 1 / 7 | |
| 2.2.9 | 1 / 7 | |
| 2.2.8 | 1 / 7 | |
| 2.2.7 | 1 / 7 | |
| 2.2.6 | 1 / 7 | |
| 2.2.4 | 1 / 7 | |
| 2.2.3 | 1 / 7 | |
| 2.2.2 | 1 / 7 | |
| 2.2.1 | 1 / 7 | |
| 2.2.0 | 1 / 7 | |
| 2.1.0 | 1 / 8 | |
| 2.0.1 | 1 / 8 | |
| 2.0.0 | 1 / 8 | |
| 1.5.9 | 1 / 7 | |
| 1.5.8 | 1 / 7 | |
| 1.5.7 | 1 / 7 | |
| 1.5.6 | 1 / 1 | |
| 1.5.5 | 1 / 1 | |
| 1.5.4 | 1 / 1 | |
| 1.5.3 | 1 / 1 | |
| 1.5.2 | 1 / 1 | |
| 1.5.1 | 1 / 1 | |
| 1.5.0 | 1 / 1 | |
| 1.4.3 | 1 / 1 | |
| 1.4.2 | 1 / 1 | |
| 1.4.1 | 1 / 1 | |
| 1.4.0 | 1 / 1 | |
| 1.3.9 | 1 / 1 | |
| 1.3.8 | 1 / 1 | |
| 1.3.7 | 1 / 1 | |
| 1.3.6 | 1 / 1 | |
| 1.3.5 | 1 / 1 | |
| 1.3.4 | 1 / 1 | |
| 1.3.3 | 1 / 1 | |
| 1.3.2 | 1 / 1 | |
| 1.3.1 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.1 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.5 | 1 / 1 | |
| 1.1.4 | 1 / 1 | |
| 1.1.3 | 1 / 1 | |
| 1.1.2 | 1 / 1 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 |
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.