@baseline-ui/translations
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:dist/index.js | AI (source-diff): Bundled tsup output with embedded locale JSON, not true obfuscation. | ai | |
| source-diff | obfuscated-file-transition:dist/index.mjs | AI (source-diff): Bundled tsup output with embedded locale JSON, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Used via config/build tooling in this monorepo package, stable false positive. | ai |
Versions (showing 51 of 99)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 | |
| 0.63.0 | 0 / 1 | |
| 0.62.0 | 0 / 1 | |
| 0.61.0 | 0 / 1 | |
| 0.60.1 | 0 / 1 | |
| 0.60.0 | 0 / 1 | |
| 0.59.0 | 0 / 1 | |
| 0.58.0 | 0 / 1 | |
| 0.57.2 | 0 / 1 | |
| 0.57.1 | 0 / 1 | |
| 0.57.0 | 0 / 1 | |
| 0.56.0 | 1 / 2 | |
| 0.55.0 | 1 / 2 | |
| 0.54.2 | 1 / 2 | |
| 0.52.0 | 1 / 2 | |
| 0.48.4 | 1 / 2 | |
| 0.46.2 | 1 / 2 | |
| 0.45.6 | 1 / 2 | |
| 0.45.5 | 1 / 2 | |
| 0.43.0 | 1 / 2 | |
| 0.42.0 | 1 / 2 | |
| 0.41.1 | 2 / 2 | |
| 0.41.0 | 2 / 2 | |
| 0.40.1 | 2 / 2 | |
| 0.40.0 | 2 / 2 | |
| 0.39.1 | 2 / 2 | |
| 0.39.0 | 2 / 2 | |
| 0.38.0 | 2 / 2 | |
| 0.37.1 | 2 / 2 | |
| 0.37.0 | 2 / 2 | |
| 0.36.0 | 2 / 2 | |
| 0.35.1 | 2 / 2 | |
| 0.35.0 | 2 / 2 | |
| 0.34.0 | 2 / 2 | |
| 0.33.1 | 2 / 2 | |
| 0.33.0 | 2 / 2 | |
| 0.32.0 | 2 / 2 | |
| 0.31.1 | 2 / 2 | |
| 0.31.0 | 2 / 2 | |
| 0.30.0 | 2 / 2 | |
| 0.29.3 | 2 / 2 | |
| 0.29.2 | 2 / 2 | |
| 0.29.1 | 2 / 2 | |
| 0.29.0 | 2 / 2 | |
| 0.28.0 | 2 / 2 | |
| 0.27.0 | 2 / 2 | |
| 0.26.0 | 2 / 2 | |
| 0.25.0 | 2 / 2 | |
| 0.24.1 | 2 / 2 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.