@aiready/components
Unified shared components library (UI, charts, hooks, utilities) for AIReady
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aiready/core | AI (phantom-deps): Same-org dependency likely re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:d3-force | AI (phantom-deps): d3-force is a declared runtime dep used by ForceDirectedGraph/useForceSimulation hooks; phantom-dep heuristic false positive. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.14.26 | 8 / 10 | |
| 0.14.25 | 8 / 10 | |
| 0.14.24 | 8 / 10 | |
| 0.14.21 | 8 / 10 | |
| 0.14.19 | 8 / 10 | |
| 0.14.16 | 8 / 10 | |
| 0.14.14 | 8 / 10 | |
| 0.14.12 | 8 / 10 | |
| 0.14.5 | 8 / 10 | |
| 0.14.0 | 8 / 10 | |
| 0.13.19 | 8 / 10 | |
| 0.13.18 | 8 / 9 | |
| 0.13.14 | 8 / 9 | |
| 0.13.4 | 8 / 9 | |
| 0.13.3 | 8 / 9 | |
| 0.12.0 | 8 / 9 | |
| 0.11.9 | 6 / 9 | |
| 0.11.8 | 6 / 9 | |
| 0.9.3 | 6 / 9 | |
| 0.8.0 | 6 / 9 | |
| 0.1.38 | 6 / 9 | |
| 0.1.37 | 6 / 9 | |
| 0.1.36 | 6 / 9 | |
| 0.1.31 | 6 / 9 | |
| 0.1.22 | 6 / 9 | |
| 0.1.19 | 6 / 9 | |
| 0.1.18 | 6 / 9 | |
| 0.1.16 | 6 / 9 | |
| 0.1.7 | 6 / 9 | |
| 0.1.4 | 6 / 9 | |
| 0.1.0 | 6 / 9 |
v0.14.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.