← Home

@aeria-ui/cli

npm

TODO: provide basic documentation.

23
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tartuffe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 23 of 23)

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
0.0.15 8 / 9
0.0.14 8 / 9
0.0.13 8 / 9
0.0.12 8 / 9
0.0.11 8 / 9
0.0.10 8 / 9
0.0.9 9 / 8
0.0.8 9 / 8
0.0.7 9 / 8
0.0.6 9 / 8
0.0.5 9 / 8
0.0.4 9 / 8
0.0.3 9 / 8

v0.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.