← Home

@qualcomm-ui/changesets-cli

npm Repository

Changeset automation CLI for conventional commits

3
Versions
BSD-3-Clause-Clear
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

mynameistechnorbowerqcom

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ts-morph AI (phantom-deps): Likely used via config/build tooling rather than direct import; not a supply-chain risk. ai
phantom-deps phantom-dep:@actions/core AI (phantom-deps): CI/CD utility dep; referenced in config files as expected for a GitHub Actions-based CLI. ai
phantom-deps phantom-dep:@octokit/rest AI (phantom-deps): GitHub API dep; referenced in config files consistent with changeset automation tooling. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.0 4 / 0
1.0.4 3 / 0
1.0.0 5 / 0

v1.1.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: GitHub Actions.

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

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