← Home

@aiready/consistency

npm Repository Homepage
11
Versions
—
License
Yes
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

caopeng

Keywords

aireadyconsistencynaming-conventionscode-patternscode-qualityai-codetech-debtrefactoringcopilotchatgptclaudeai-assisted-developmentarchitecturebest-practices

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. ai
phantom-deps phantom-dep:@typescript-eslint/types AI (phantom-deps): Declared dep used transitively via typescript-estree; stable FP for this package. ai
install-scripts install-script:preinstall AI (install-scripts): Script only creates dist dir and empty cli.js stub; no network or arbitrary code execution. ai

Versions (showing 11 of 11)

Version Deps Published
0.21.32 5 / 4
0.21.31 5 / 4
0.21.30 5 / 4
0.21.27 5 / 4
0.8.36 5 / 4
0.8.11 5 / 4
0.6.13 5 / 4
0.6.10 5 / 4
0.2.5 3 / 4
0.2.3 3 / 4
0.2.2 3 / 4

v0.21.32

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: mkdir -p dist && touch dist/cli.js

LOW No provenance attestation provenance

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

v0.21.31

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.21.30

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.21.27

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.8.36

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.8.11

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.6.13

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.6.10

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.2.5

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.2.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.

v0.2.2

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.