@octaviaflow/icons
Icons for digital and software products using the OctaviaFlow 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/index.cjs | AI (source-diff): Sample shows readable bundled React/SVG icon code; long lines are from bundled SVG paths, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Same as index.cjs — ESM bundle of icon components, not obfuscated. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a legitimate utility; phantom-dep heuristic fires because it's used in config/build rather than directly imported in reviewed source. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped design-system icons package; edit-distance match to 'cors' is a heuristic false positive with no semantic similarity. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): ora is a build-time CLI dependency used in tasks scripts; not imported in runtime code. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a build-time CLI dependency used in tasks scripts; not imported in runtime code. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.18 | 1 / 14 | |
| 3.0.2 | 1 / 14 | |
| 3.0.1 | 1 / 14 | |
| 3.0.0 | 1 / 14 | |
| 2.0.0 | 2 / 6 |
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.