← Home

@citation-js/cli

npm Repository Homepage
13
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

larsgw

Keywords

citation-jscli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Established monorepo with long history and trusted publisher; dormancy is normal cadence. ai
dependencies unvetted-dep:@citation-js/core AI (dependencies): First-party sibling package in same monorepo. ai
dependencies unvetted-dep:@citation-js/plugin-doi AI (dependencies): First-party sibling package in same monorepo. ai
semgrep semgrep:dynamic-require AI (semgrep): Plugin-loader pattern constrained to @citation-js/plugin-* namespace; stable across versions. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @citation-js/cli with 2700+ day history; no relation to joi. ai

Versions (showing 13 of 13)

Version Deps Published
0.8.2 8 / 0
0.8.1 8 / 0
0.8.0 8 / 0
0.7.22 8 / 0
0.7.21 8 / 0
0.7.20 8 / 0
0.7.19 8 / 0
0.7.18 8 / 0
0.7.17 8 / 0
0.7.16 8 / 0
0.7.15 8 / 0
0.7.14 8 / 0
0.7.13 8 / 0

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.1

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

1 finding
LOW No provenance attestation provenance

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

v0.7.18

1 finding
LOW No provenance attestation provenance

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

v0.7.17

1 finding
LOW No provenance attestation provenance

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

v0.7.16

1 finding
LOW No provenance attestation provenance

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

v0.7.15

1 finding
LOW No provenance attestation provenance

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

v0.7.14

1 finding
LOW No provenance attestation provenance

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

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