@aivenio/aquarium
Aiven Aquarium design system
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/src/molecules/CommandPalette/CommandPalette.js | AI (source-diff): Compiled TypeScript output; long lines are bundled React code, not obfuscation. Stable pattern for this design system package. | ai | |
| source-diff | obfuscated-file:dist/src/molecules/CommandPalette/CommandPaletteProvider.js | AI (source-diff): Same as above — compiled TS/React output with readable logic, not obfuscated. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a well-known animation library; stable false positive for this design system package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 11 / 70 | |
| 6.1.1 | 11 / 70 | |
| 6.0.1 | 11 / 71 | |
| 6.0.0 | 11 / 71 | |
| 5.4.0 | 11 / 89 | |
| 5.3.2 | 11 / 89 | |
| 5.3.1 | 11 / 89 | |
| 4.8.2 | 11 / 89 | |
| 4.8.1 | 11 / 89 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.