@formatjs/intl
Internationalize JS apps. This library provides an API to format dates, numbers, and strings, including pluralization and handling translations.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 3.1M weekly downloads and 2000+ day history; lack of provenance attestation is not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper implicitly required by compiled output; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@formatjs/intl-listformat | AI (dependencies): First-party formatjs monorepo package published by the same trusted author (longlho); not a third-party risk. | ai | |
| dependencies | unvetted-dep:@formatjs/intl-displaynames | AI (dependencies): First-party formatjs monorepo package published by the same trusted author (longlho); not a third-party risk. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from individual (longlho) to GitHub Actions CI/CD with SLSA provenance. This is a legitimate and security-improving transition for the formatjs project. | ai | |
| dependencies | unvetted-dep:@formatjs/fast-memoize | AI (dependencies): @formatjs/fast-memoize is a first-party formatjs ecosystem package published by the same maintainer team in the same monorepo. | ai | |
| dependencies | unvetted-dep:@formatjs/icu-messageformat-parser | AI (dependencies): @formatjs/icu-messageformat-parser is a first-party formatjs ecosystem package published by the same maintainer team in the same monorepo. | ai | |
| dependencies | unvetted-dep:intl-messageformat | AI (dependencies): intl-messageformat is a first-party formatjs ecosystem package published by the same maintainer team in the same monorepo. | ai | |
| dependencies | unvetted-dep:@formatjs/ecma402-abstract | AI (dependencies): Sibling package in the same @formatjs monorepo (formatjs/formatjs); legitimate and well-known dependency used throughout the FormatJS ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package has 183 versions, 2070 days of history, and 3.1M weekly downloads. The inflated-semver signal is a false positive triggered by first review, not a new package. | ai |
Versions (showing 51 of 156)
| Version | Deps | Published |
|---|---|---|
| 4.1.12 | 3 / 0 | |
| 4.1.11 | 3 / 0 | |
| 4.1.10 | 3 / 0 | |
| 4.1.9 | 3 / 0 | |
| 4.1.8 | 3 / 0 | |
| 4.1.7 | 3 / 0 | |
| 4.1.6 | 3 / 0 | |
| 4.1.5 | 4 / 0 | |
| 4.1.4 | 4 / 0 | |
| 4.1.3 | 4 / 0 | |
| 4.1.2 | 5 / 0 | |
| 4.1.1 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.9 | 5 / 0 | |
| 4.0.8 | 5 / 0 | |
| 4.0.7 | 5 / 0 | |
| 4.0.6 | 5 / 0 | |
| 4.0.5 | 5 / 0 | |
| 4.0.4 | 5 / 0 | |
| 4.0.2 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.1.8 | 5 / 0 | |
| 3.1.7 | 5 / 0 | |
| 3.1.6 | 5 / 0 | |
| 3.1.5 | 5 / 0 | |
| 3.1.4 | 5 / 0 | |
| 3.1.3 | 5 / 0 | |
| 3.1.2 | 5 / 0 | |
| 3.1.1 | 5 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.4 | 5 / 0 | |
| 3.0.3 | 5 / 0 | |
| 3.0.2 | 5 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 5 / 0 | |
| 2.10.15 | 7 / 2 | |
| 2.10.14 | 7 / 2 | |
| 2.10.13 | 7 / 2 | |
| 2.10.12 | 7 / 2 | |
| 2.10.11 | 7 / 2 | |
| 2.10.10 | 7 / 2 | |
| 2.10.9 | 7 / 2 | |
| 2.10.8 | 7 / 2 | |
| 2.10.7 | 7 / 2 | |
| 2.10.6 | 7 / 2 | |
| 2.10.5 | 7 / 2 | |
| 2.10.4 | 7 / 2 | |
| 2.10.3 | 7 / 2 | |
| 2.10.2 | 7 / 2 | |
| 2.3.4 | 7 / 2 |
v4.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.4
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.
v4.1.3
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.
v4.1.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.
v4.1.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.
v4.1.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.
v4.0.9
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.
v4.0.8
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.
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.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. 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.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: longlho.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: longlho.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.