← Home

@changesets/logger

npm Repository Homepage

Console log alias

8
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
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only dependency commonly declared without direct imports; no risk. ai
provenance publisher-changed AI (provenance): mitchellhamilton is the primary author of the changesets project; the transition from noviny is a legitimate maintainer handoff within the same org, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): mitchellhamilton is the canonical changesets maintainer; this addition reflects a legitimate org-level maintainer transition. ai
phantom-deps phantom-dep:@changesets/types AI (phantom-deps): Same-org scoped types package; phantom-dep finding is a false positive for type-only usage within the monorepo. ai

Versions (showing 8 of 8)

Hide prereleases
Version Deps Published
0.1.1 1 / 0
0.1.0 1 / 0
0.0.5 1 / 0
0.0.4 1 / 0
0.0.3 1 / 0
0.0.2 3 / 2
0.0.1 3 / 2
1.0.0-next.1 1 / 1

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.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 2019-11-04) provenance

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

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

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.