← Home

@changesets/errors

npm Repository Homepage

Error classes for @changesets

7
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

andaristemmatownnovinychangesets-release-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): mitchellhamilton is a core changesets maintainer with an exemplary track record (1307 approved, 0 rejected). The noviny→mitchellhamilton transition is a known legitimate handoff within the changesets project. ai
maintainer-change maintainer-added AI (maintainer-change): mitchellhamilton is a well-established, trusted publisher in the changesets ecosystem. Addition is a legitimate maintainer transition, not a takeover. ai
bogus-package bogus-package AI (bogus-package): Internal utility package in a monorepo; sparse README and no keywords are expected for this type of package. ai

Versions (showing 7 of 7)

Hide prereleases
Version Deps Published
0.2.0 1 / 0
0.1.4 1 / 0
0.1.3 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0
0.1.0 0 / 0
1.0.0-next.1 0 / 0

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

1 finding
LOW No provenance attestation provenance

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

v0.1.3

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: mitchellhamilton → changesets-release-bot (on 2020-03-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-29. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.2

2 findings
HIGH Publisher changed: noviny → mitchellhamilton (on 2019-10-31) provenance

This version was published by a different npm account than previous versions on 2019-10-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.1

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.