@resourge/translations
[](LICENSE)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:import-sync | AI (dependencies): import-sync is a legitimate sync-require utility; its use in a build/translation tool is expected and not a risk indicator. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 3 / 0 | |
| 1.11.1 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.10 | 3 / 0 | |
| 1.10.9 | 3 / 0 | |
| 1.10.8 | 3 / 0 | |
| 1.10.7 | 3 / 0 | |
| 1.10.6 | 3 / 0 | |
| 1.10.5 | 1 / 0 | |
| 1.10.4 | 1 / 0 |
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.