unified
parse, inspect, transform, and serialize content through syntax trees
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/vfile | AI (phantom-deps): @types/vfile is a TypeScript type package loaded by convention, not direct import. This is expected behavior for type-only dependencies in this package. | ai | |
| dependencies | unvetted-dep:@types/vfile | AI (dependencies): @types/vfile is a DefinitelyTyped type definition package added to support TypeScript declarations; benign and appropriate for this package's TypeScript support addition. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from v10 to v11 is explained by TypeScript type definitions and build output additions; consistent with a major version bump for this well-established package. | ai | |
| dependencies | unvetted-dep:attach-ware | AI (dependencies): attach-ware is a wooorm-authored package in the unified ecosystem, consistent with this package's build scripts and publisher track record. Not a meaningful risk. | ai | |
| dependencies | unvetted-dep:devlop | AI (dependencies): devlop is a development utility by wooorm (the package author); stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@types/unist, @ungap/structured-clone, devlop) are all legitimate, well-known packages in the unified ecosystem added as part of a major version modernization. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): @types/unist is a scoped type package loaded by TypeScript convention; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): wooorm's packages consistently lack Sigstore provenance; this is a stable characteristic of this publisher, not a risk signal. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 11.0.5 | 7 / 12 | |
| 11.0.4 | 7 / 12 | |
| 11.0.3 | 7 / 12 | |
| 11.0.2 | 7 / 12 | |
| 11.0.1 | 7 / 12 | |
| 11.0.0 | 7 / 12 | |
| 10.1.2 | 7 / 12 | |
| 10.1.1 | 7 / 12 | |
| 10.1.0 | 7 / 12 | |
| 10.0.1 | 7 / 12 | |
| 10.0.0 | 7 / 12 | |
| 9.2.2 | 6 / 10 | |
| 9.2.1 | 6 / 9 | |
| 9.2.0 | 6 / 9 | |
| 9.1.0 | 6 / 9 | |
| 9.0.0 | 6 / 9 | |
| 8.4.2 | 5 / 9 | |
| 8.4.1 | 5 / 10 | |
| 8.4.0 | 5 / 10 | |
| 8.3.2 | 5 / 10 | |
| 8.3.1 | 5 / 10 | |
| 8.3.0 | 5 / 10 | |
| 8.2.0 | 5 / 10 | |
| 8.1.0 | 5 / 10 | |
| 8.0.1 | 5 / 10 | |
| 8.0.0 | 5 / 12 | |
| 7.1.0 | 8 / 10 | |
| 7.0.2 | 6 / 8 | |
| 7.0.1 | 6 / 8 | |
| 7.0.0 | 6 / 8 | |
| 6.2.0 | 6 / 8 | |
| 6.1.6 | 7 / 7 | |
| 6.1.5 | 7 / 7 | |
| 6.1.4 | 8 / 7 | |
| 6.1.3 | 8 / 7 | |
| 6.1.2 | 9 / 7 | |
| 6.1.1 | 9 / 7 | |
| 6.1.0 | 9 / 7 | |
| 6.0.0 | 8 / 7 | |
| 5.1.0 | 8 / 7 | |
| 5.0.0 | 8 / 11 | |
| 4.2.1 | 6 / 11 | |
| 4.2.0 | 6 / 11 | |
| 4.1.2 | 4 / 13 | |
| 4.1.1 | 4 / 13 | |
| 4.1.0 | 4 / 13 | |
| 4.0.1 | 3 / 13 | |
| 4.0.0 | 3 / 13 | |
| 3.0.0 | 6 / 13 | |
| 2.1.4 | 6 / 14 | |
| 2.1.2 | 6 / 14 | |
| 2.1.1 | 6 / 14 | |
| 2.1.0 | 6 / 14 | |
| 2.0.0 | 5 / 14 | |
| 1.0.0 | 5 / 14 |
v11.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.