@lingui/core
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 | publisher-changed | AI (provenance): Transition from named maintainer to GitHub Actions is a legitimate CI/CD automation pattern, confirmed by SLSA provenance attestation from the official lingui/js-lingui repo. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a build-time injected dependency for Babel-compiled packages; not directly imported in source is expected and stable for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @lingui/core is a scoped package in the well-established js-lingui i18n monorepo with 3033 days of history. The Levenshtein match to 'cors' is purely coincidental and not a typosquat. | ai | |
| dependencies | unvetted-dep:@lingui/message-utils | AI (dependencies): First-party dependency from the same @lingui monorepo, published at the same version. Not a third-party risk. | ai | |
| dependencies | unvetted-dep:@lingui/babel-plugin-lingui-macro | AI (dependencies): First-party dependency from the same @lingui monorepo, published at the same version. Not a third-party risk. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 2 / 3 | |
| 6.0.1 | 2 / 3 | |
| 6.0.0 | 2 / 3 | |
| 5.9.5 | 2 / 2 | |
| 5.9.4 | 2 / 2 | |
| 5.9.3 | 2 / 2 | |
| 5.9.2 | 2 / 2 | |
| 5.9.1 | 2 / 2 | |
| 5.9.0 | 2 / 2 | |
| 5.8.0 | 2 / 2 | |
| 5.7.0 | 2 / 2 | |
| 5.6.1 | 2 / 2 | |
| 5.6.0 | 2 / 2 | |
| 5.5.2 | 2 / 2 | |
| 5.5.1 | 2 / 2 | |
| 5.5.0 | 2 / 2 | |
| 5.4.1 | 2 / 2 | |
| 5.4.0 | 2 / 2 | |
| 5.3.3 | 2 / 2 | |
| 5.3.2 | 3 / 2 | |
| 5.3.1 | 3 / 3 | |
| 5.3.0 | 3 / 3 | |
| 5.2.0 | 3 / 3 | |
| 5.1.2 | 3 / 3 | |
| 5.1.1 | 3 / 3 | |
| 5.1.0 | 3 / 3 | |
| 5.0.0 | 3 / 3 | |
| 4.14.1 | 3 / 2 | |
| 4.14.0 | 3 / 2 | |
| 4.13.0 | 3 / 2 | |
| 4.12.0 | 3 / 2 | |
| 4.11.4 | 3 / 2 | |
| 4.11.3 | 3 / 2 | |
| 4.11.2 | 3 / 2 | |
| 4.11.1 | 3 / 2 | |
| 4.11.0 | 3 / 2 | |
| 4.10.1 | 3 / 2 |
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
2 findingsPackage name '@lingui/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-10. 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.
v5.5.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.