← Home

@changesets/get-version-range-type

npm Repository Homepage

Common get-version-range-type shared between changeset packages

10
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
npm-metadata suspicious-initial-version AI (npm-metadata): The @changesets monorepo intentionally uses 0.0.0 for internal utility packages. This is a stable pattern for this publisher and package, not a malware indicator. ai
provenance publisher-changed AI (provenance): Transition from noviny to changesets-release-bot is the documented official maintainer handoff for the changesets project; stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): changesets-release-bot and mitchellhamilton are the official maintainers of the changesets project; this is a legitimate transition. ai
bogus-package bogus-package AI (bogus-package): Small utility package in a monorepo; short README, no keywords, and no runtime deps are expected and benign for this type of focused utility module. ai

Versions (showing 10 of 10)

Hide prereleases
Version Deps Published
0.4.0 0 / 0
0.3.2 0 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.2 0 / 0
0.0.0 0 / 0
1.0.0-next.1 0 / 0

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

2 findings
HIGH Publisher changed: noviny → changesets-release-bot (on 2020-02-01) provenance

This version was published by a different npm account than previous versions on 2020-02-01. 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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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