← Home

eslint-plugin-command

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

antfu

Keywords

eslint-plugincodemod

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Trusted publisher; publish-env metadata change, no behavioral risk. ai
provenance no-provenance AI (provenance): Absence of Sigstore attestation is not a risk for this established package. ai

Versions (showing 10 of 10)

Version Deps Published
3.5.3 1 / 28
3.5.2 1 / 27
3.5.1 1 / 27
3.4.0 1 / 25
3.3.1 1 / 27
3.3.0 1 / 27
3.2.1 1 / 27
3.2.0 1 / 27
3.1.0 1 / 28
3.0.0 1 / 28

v3.5.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.2.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

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