← Home

@changesets/write

npm Repository Homepage

Writes a changeset to a file

18
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

novinychangesets-release-botemmatownandarist

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): emmatown is a known changesets contributor; this reflects a documented maintainer transition within the changesets project, not a takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): mitchellhamilton's removal is part of the same known transition; the changesets project has moved to new maintainers legitimately. ai
semgrep semgrep:dynamic-require AI (semgrep): Pattern is a standard optional peer-dep resolution for prettier from the consumer's cwd — not arbitrary module loading. ai
typosquat typosquat.levenshtein:vite AI (typosquat): @changesets/write is a legitimate scoped package in the changesets monorepo; the Levenshtein match to 'vite' is a false positive with no plausible impersonation intent. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): @babel/runtime is a standard Babel transpilation runtime helper; declaring it as a dependency without direct imports is the expected pattern for Babel-compiled packages. ai

Versions (showing 18 of 18)

Show 1 prerelease
Version Deps Published
0.4.0 4 / 2
0.3.2 4 / 2
0.3.1 5 / 2
0.3.0 5 / 2
0.2.3 5 / 2
0.2.2 5 / 2
0.2.1 5 / 2
0.2.0 5 / 2
0.1.9 5 / 2
0.1.8 5 / 2
0.1.7 5 / 2
0.1.6 5 / 2
0.1.5 5 / 2
0.1.4 5 / 2
0.1.3 5 / 2
0.1.2 5 / 2
0.1.1 5 / 2
0.1.0 5 / 2

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

1 finding
LOW No provenance attestation provenance

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

v0.2.2

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

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

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

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