@telegraph/tokens
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:dist/cjs/css-variables-map.js | AI (source-diff): Long-line JSON token map, not obfuscation; stable build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/flattened-css-variables-map.js | AI (source-diff): Long-line JSON token map, not obfuscation; stable build output. | ai | |
| source-diff | obfuscated-file:dist/esm/css-variables-map.mjs | AI (source-diff): Long-line JSON token map, not obfuscation; stable build output. | ai | |
| source-diff | obfuscated-file:dist/esm/flattened-css-variables-map.mjs | AI (source-diff): Long-line JSON token map, not obfuscation; stable build output. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 0 / 9 | |
| 0.2.1 | 0 / 9 | |
| 0.2.0 | 0 / 9 | |
| 0.1.4 | 0 / 9 | |
| 0.1.3 | 0 / 9 | |
| 0.1.2 | 0 / 9 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 | |
| 0.0.22 | 0 / 9 | |
| 0.0.21 | 0 / 9 | |
| 0.0.20 | 0 / 9 | |
| 0.0.19 | 0 / 9 | |
| 0.0.18 | 0 / 9 | |
| 0.0.15 | 0 / 9 | |
| 0.0.13 | 0 / 9 | |
| 0.0.12 | 0 / 9 | |
| 0.0.11 | 0 / 8 | |
| 0.0.10 | 0 / 8 | |
| 0.0.9 | 0 / 8 |
v0.2.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.