← Home

@cipherstash/cli

npm

CipherStash CLI — the one stash command for auth, init, encryption schema, database setup, and secrets.

13
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

cs_lindsaydrew_cipherstashjames-sadlerdan-drapercs-zcjbrewer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): CipherStash CLI; low-risk package, no other red flags; provenance absence alone is insufficient to block. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @cipherstash/cli is not a plausible typosquat of joi; Levenshtein match is spurious. ai
phantom-deps phantom-dep:picocolors AI (phantom-deps): CLI tool; picocolors is a declared runtime dep, heuristic false positive. ai
phantom-deps phantom-dep:posthog-node AI (phantom-deps): posthog-node is a declared runtime dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
0.10.1 8 / 8
0.10.0 8 / 8
0.9.0 8 / 6
0.8.0 9 / 6
0.7.1 9 / 6
0.7.0 9 / 6
0.6.1 9 / 6
0.6.0 9 / 6
0.5.0 9 / 6
0.4.0 9 / 6
0.3.0 9 / 6
0.2.0 9 / 6
0.1.0 9 / 6

v0.10.1

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

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

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

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

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.