@aeria-ui/cli
TODO: provide basic documentation.
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:joi | AI (typosquat): Scoped package @aeria-ui/cli is unrelated to joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): Build tool dependency used via config convention, not direct import. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Build tool dependency used via config convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-node-resolve | AI (phantom-deps): Framework-scoped build plugin loaded by convention, not direct import. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.25 | 8 / 9 | |
| 0.0.24 | 8 / 9 | |
| 0.0.23 | 8 / 9 | |
| 0.0.22 | 8 / 9 | |
| 0.0.21 | 8 / 9 | |
| 0.0.20 | 8 / 9 | |
| 0.0.19 | 8 / 9 | |
| 0.0.18 | 8 / 9 | |
| 0.0.17 | 8 / 9 | |
| 0.0.16 | 8 / 9 |
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.