@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, 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/src/molecules/ChoiceChipGroup/ChoiceChipGroup.js | AI (source-diff): Long-line compiled TS output, readable React source, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/charts/Treemap/Treemap.js | AI (source-diff): Long line is transpiled/bundled TS output, not obfuscation; code is plainly readable. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): clsx is a well-known, widely used utility replacing classnames; benign dep swap. | ai | |
| 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 6.7.0 | 11 / 70 | |
| 6.6.0 | 11 / 70 | |
| 6.5.0 | 11 / 70 | |
| 6.4.0 | 11 / 70 | |
| 6.3.0 | 11 / 70 | |
| 6.2.0 | 11 / 70 | |
| 6.1.1 | 11 / 70 | |
| 6.1.0 | 11 / 70 | |
| 6.0.2 | 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 | |
| 5.3.0 | 11 / 89 | |
| 5.2.0 | 11 / 89 | |
| 5.1.0 | 11 / 89 | |
| 5.0.1 | 11 / 89 | |
| 5.0.0 | 11 / 89 | |
| 4.9.0 | 11 / 89 | |
| 4.8.2 | 11 / 89 | |
| 4.8.1 | 11 / 89 |
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
4 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2026-02-25, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.2.0
4 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2026-02-18, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.1.0
4 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2026-02-17, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.1
4 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2026-02-11, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.0
4 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2026-02-11, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.9.0
3 findingsNewly 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.
This version was published by a different npm account (pousi-aiven) than the most recent previously approved version (aiven-npm-release-bot) on 2025-12-29, but pousi-aiven is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.