@changesets/parse 1.0.0-next.8
Parse a changeset file's contents into a usable json object
@changesets/parse@1.0.0-next.8 was published on 2026-07-17. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^22.11 || ^24 || >=26.
All @changesets/parse versions · Permanent reference to 1.0.0-next.8 · Latest release
Package specifications
| Version | 1.0.0-next.8 |
|---|---|
| License declaration | MIT |
| Published | 2026-07-17T12:03:23.826Z |
| Node.js requirement | ^22.11 || ^24 || >=26 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 6.03 KiB |
| Published file count | 5 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 12533 |
| Repository forks | 854 |
Install @changesets/parse 1.0.0-next.8
npm install @changesets/parse@1.0.0-next.8 pnpm add @changesets/parse@1.0.0-next.8 yarn add @changesets/parse@1.0.0-next.8
Runtime dependencies
- yaml ^2.9.0
- @changesets/types ^7.0.0-next.7
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @changesets/types@7.0.0 — direct
- yaml@2.9.1 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 10/10 — all changesets reviewed |
|---|---|
| Maintained | 10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Pinned-Dependencies | 4/10 — dependency not pinned by hash detected -- score normalized to 4 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 4/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/%40changesets%2Fparse/1.0.0-next.8 — retrieved 2026-10-29T12:02:40.881Z
- https://api.deps.dev/v3/projects/github.com%2Fchangesets%2Fchangesets — retrieved 2026-10-29T07:15:03.244Z
- https://api.deps.dev/v3/systems/npm/packages/%40changesets%2Fparse/versions/1.0.0-next.8 — retrieved 2026-10-29T12:02:41.418Z
- https://api.deps.dev/v3/systems/npm/packages/%40changesets%2Fparse/versions/1.0.0-next.8:dependencies — retrieved 2026-10-29T12:02:41.439Z