@octaviaflow/core
OctaviaFlow Design System React components
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @octaviaflow/core is a scoped design system package; similarity to 'cors' is coincidental and not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:@octaviaflow/fonts | AI (phantom-deps): Same-org sibling package in a monorepo design system; declared as a runtime dependency, not a phantom. | ai | |
| phantom-deps | phantom-dep:@octaviaflow/icons | AI (phantom-deps): Same-org sibling package in a monorepo design system; declared as a runtime dependency, not a phantom. | ai | |
| phantom-deps | phantom-dep:@octaviaflow/tokens | AI (phantom-deps): Same-org sibling package in a monorepo design system; declared as a runtime dependency, not a phantom. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.0.18 | 7 / 16 | |
| 3.0.14 | 7 / 16 | |
| 3.0.13 | 7 / 16 | |
| 3.0.12 | 7 / 16 | |
| 3.0.11 | 7 / 16 | |
| 3.0.10 | 7 / 16 | |
| 3.0.9 | 7 / 16 | |
| 3.0.8 | 7 / 16 | |
| 3.0.7 | 7 / 16 | |
| 3.0.6 | 7 / 16 | |
| 3.0.5 | 7 / 16 | |
| 3.0.4 | 7 / 16 | |
| 3.0.3 | 7 / 16 | |
| 3.0.2 | 7 / 16 | |
| 3.0.1 | 7 / 16 | |
| 3.0.0 | 7 / 16 |
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
2 findingsPackage name '@octaviaflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.