← Home

@stricli/auto-complete

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

bloomberg-ossbbgbuildermolisani

Versions (showing 14 of 14)

Version Deps Published
1.3.0 1 / 8
1.2.9 1 / 8
1.2.8 1 / 8
1.2.7 1 / 8
1.2.6 1 / 8
1.2.5 1 / 8
1.2.4 1 / 8
1.2.1 1 / 8
1.2.0 1 / 8
1.1.2 1 / 8
1.1.1 1 / 8
1.1.0 1 / 8
1.0.1 1 / 8
1.0.0 1 / 8

v1.3.0

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.

v1.2.9

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.

v1.1.2

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

INFO Publisher changed: molisani → bbgbuilder (on 2025-03-27, now via trusted publisher with provenance) provenance

This version was published by a different npm account (bbgbuilder) than the most recent previously approved version (molisani) on 2025-03-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: bbgbuilder → molisani (on 2024-10-22, known maintainer) provenance

This version was published by a different npm account (molisani) than the most recent previously approved version (bbgbuilder) on 2024-10-22, but molisani is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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