@adyen/ui-assets-icons-40
Adyen UI Assets for 40px systems
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adyen migrated publishing to GitHub Actions CI; consistent with official org automation. | ai | |
| source-diff | obfuscated-file:dist/abacus.js | AI (source-diff): Vite-bundled Vue SVG icon component; long lines are SVG path data, not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/acquiring.js | AI (source-diff): Same pattern: Vite-bundled Vue SVG icon component with long SVG path data lines. | ai | |
| source-diff | obfuscated-file:dist/adyen-for-platforms-advanced.js | AI (source-diff): Same pattern: Vite-bundled Vue SVG icon component with long SVG path data lines. | ai | |
| source-diff | obfuscated-file:dist/android-logo.js | AI (source-diff): Same pattern: Vite-bundled Vue SVG icon component with long SVG path data lines. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library; bulk addition of per-icon JS files is expected behavior for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 4.10.7 | 0 / 4 | |
| 4.10.6 | 0 / 4 | |
| 4.10.5 | 0 / 4 | |
| 4.10.4 | 0 / 4 | |
| 4.10.3 | 0 / 4 | |
| 4.10.2 | 0 / 4 | |
| 4.10.1 | 0 / 4 | |
| 4.10.0 | 0 / 4 | |
| 4.9.7 | 0 / 4 | |
| 4.9.6 | 0 / 4 | |
| 4.9.4 | 0 / 4 | |
| 4.9.3 | 0 / 4 | |
| 4.9.2 | 0 / 4 | |
| 4.9.1 | 0 / 4 | |
| 4.9.0 | 0 / 4 | |
| 4.8.4 | 0 / 4 | |
| 4.8.3 | 0 / 4 | |
| 4.8.2 | 0 / 4 | |
| 4.8.1 | 0 / 4 | |
| 4.8.0 | 0 / 4 | |
| 4.7.4 | 0 / 4 | |
| 4.7.3 | 0 / 4 | |
| 4.7.2 | 0 / 4 | |
| 4.7.1 | 0 / 4 | |
| 4.7.0 | 0 / 4 | |
| 4.6.4 | 0 / 4 | |
| 4.6.3 | 0 / 4 | |
| 4.6.2 | 0 / 4 | |
| 4.6.1 | 0 / 4 | |
| 4.6.0 | 0 / 4 | |
| 4.5.0 | 0 / 4 | |
| 4.4.2 | 0 / 4 | |
| 4.4.1 | 0 / 4 | |
| 4.4.0 | 0 / 4 | |
| 4.3.2 | 0 / 4 | |
| 4.3.1 | 0 / 4 | |
| 4.3.0 | 0 / 4 | |
| 4.2.1 | 0 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 4 | |
| 4.0.2 | 0 / 1 | |
| 4.0.1 | 0 / 1 | |
| 4.0.0 | 0 / 1 |
v4.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.