@financial-times/o3-foundation
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase from added token files, consistent with package purpose. | ai | |
| source-diff | obfuscated-file:esm/tokens/sustainable-views.js | AI (source-diff): Auto-generated design-token data file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/tokens/whitelabel.js | AI (source-diff): Auto-generated design-token data file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/tokens/core.js | AI (source-diff): Auto-generated design-token data file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/tokens/internal.js | AI (source-diff): Auto-generated design-token data file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/tokens/professional.js | AI (source-diff): Auto-generated design-token data file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm/tokens/icons.js | AI (source-diff): Auto-generated SVG icon token file; long lines are SVG path data, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:esm/tokens/icons-named.js | AI (source-diff): Auto-generated SVG icon token file; long lines are SVG path data, not obfuscation. Stable pattern for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 3.14.0 | 0 / 2 | |
| 3.13.0 | 0 / 2 | |
| 3.12.1 | 0 / 2 | |
| 3.12.0 | 0 / 2 | |
| 3.11.3 | 0 / 2 | |
| 3.11.1 | 0 / 2 | |
| 3.11.0 | 0 / 2 | |
| 3.10.1 | 0 / 2 | |
| 3.10.0 | 0 / 2 | |
| 3.9.0 | 0 / 2 | |
| 3.8.1 | 0 / 2 | |
| 3.8.0 | 0 / 2 | |
| 3.7.0 | 0 / 2 | |
| 3.6.2 | 0 / 2 | |
| 3.6.1 | 0 / 2 | |
| 3.6.0 | 0 / 2 | |
| 3.5.2 | 0 / 2 | |
| 3.5.1 | 0 / 2 | |
| 3.5.0 | 0 / 1 | |
| 3.4.0 | 0 / 1 | |
| 3.3.0 | 0 / 1 | |
| 3.2.4 | 0 / 1 | |
| 3.2.3 | 0 / 1 | |
| 3.2.2 | 0 / 1 | |
| 3.2.1 | 0 / 1 | |
| 3.2.0 | 0 / 1 | |
| 3.1.0 | 0 / 1 | |
| 3.0.1 | 0 / 1 | |
| 3.0.0 | 0 / 1 |
v3.6.0
6 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.
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.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.