← Home

@rcompat/cli

npm Repository

Standard library CLI

25
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

terrablue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Same-org sibling package, normal dependency growth. ai
source-diff large-new-source-files AI (source-diff): Legitimate library growth, no malicious payload indicators. ai
source-diff source-size-tripled AI (source-diff): Consistent with added source files, not obfuscated/injected. ai
dependencies unvetted-dep:@rcompat/stdio AI (dependencies): Sibling package in same monorepo/publisher, not an unrelated third party. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @rcompat/cli package in an established monorepo; Levenshtein match to 'joi' is a false positive. ai
phantom-deps phantom-dep:@rcompat/fs AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages that re-export or use indirect imports. ai

Versions (showing 25 of 25)

Version Deps Published
0.25.0 3 / 0
0.24.0 3 / 0
0.23.0 3 / 0
0.22.0 3 / 0
0.21.0 2 / 0
0.20.0 2 / 0
0.19.0 2 / 0
0.18.1 2 / 0
0.18.0 2 / 0
0.17.0 2 / 0
0.16.0 2 / 0
0.15.0 2 / 0
0.14.0 2 / 0
0.13.0 2 / 0
0.12.0 2 / 0
0.11.3 2 / 0
0.8.1 1 / 0
0.8.0 1 / 0
0.7.0 1 / 0
0.5.1 1 / 0
0.5.0 0 / 0
0.4.0 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v0.11.3

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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.