@changesets/parse MIT 25 versions

@changesets/parse

npm Repository Homepage

Parse a changeset file's contents into a usable json object

25

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

novinychangesets-release-botemmatownandarist

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:parcel	AI (typosquat): @changesets/parse is a legitimate scoped package in the well-known changesets monorepo; the Levenshtein match to 'parcel' is purely coincidental and not a typosquat.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed from changesets-release-bot to GitHub Actions as part of a legitimate CI/CD migration; SLSA provenance attestation confirms integrity. This is a stable pattern for the changesets monorepo.	ai	2026/04/23

Versions (showing 25 of 25)

Show 1 prerelease

Version	Deps	Published
0.4.3	2 / 2	2026-03-03
0.4.2	2 / 2	2025-11-27
0.4.1	2 / 1	2025-02-17
0.4.0	2 / 1	2023-11-28
0.3.16	2 / 1	2022-12-18
0.3.15	2 / 1	2022-10-01
0.3.14	2 / 1	2022-07-22
0.3.13	2 / 1	2022-03-27
0.3.12	2 / 1	2022-02-19
0.3.11	2 / 1	2022-01-24
0.3.10	2 / 1	2021-11-26
0.3.9	2 / 1	2021-08-31
0.3.8	2 / 1	2021-04-08
0.3.7	2 / 1	2020-10-01
0.3.6	2 / 1	2020-05-11
0.3.5	2 / 2	2020-04-15
0.3.4	2 / 2	2020-04-15
0.3.3	2 / 2	2020-03-29
0.3.2	2 / 2	2020-03-11
0.3.1	2 / 2	2019-10-31
0.3.0	2 / 2	2019-10-15
0.2.1	2 / 2	2019-09-19
0.2.0	2 / 2	2019-09-13
0.1.2	2 / 2	2019-09-10
0.1.0	2 / 2	2019-09-10

v0.4.3

2 findings

HIGH Publisher changed: changesets-release-bot → GitHub Actions (on 2026-03-03) provenance

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

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.

v0.4.2

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.

v0.4.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.15

1 finding

LOW No provenance attestation provenance

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

v0.3.14

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

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

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-11) provenance

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

v0.3.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: noviny → mitchellhamilton (on 2019-10-31) provenance

[Accepted risk] 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.

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.2

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.