vfile
Virtual file format for text processing
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@types/unist, vfile-message) are legitimate unified-ecosystem packages expected for vfile's TypeScript-enabled major version. Not a supply-chain risk. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 6KB to 28KB explained by TypeScript declarations, browser shims, and modular restructuring in this major version bump. No obfuscation or payload indicators. | ai | |
| dependencies | unvetted-dep:unist-util-stringify-position | AI (dependencies): unist-util-stringify-position is a core utility in the unified ecosystem, maintained by the same author (wooorm). It is a stable, expected dependency for vfile. | ai | |
| phantom-deps | phantom-dep:unist-util-stringify-position | AI (phantom-deps): unist-util-stringify-position is a declared runtime dependency in vfile; it's used indirectly through the package's own module graph. Phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): vfile is a long-established package (3923 days old) from a highly trusted publisher; lack of provenance attestation is expected for packages predating Sigstore adoption. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): vfile is an established package with distinct purpose (virtual file format); coincidental edit distance to vite does not indicate typosquatting. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): @types/unist is a TypeScript type package used for type resolution in the unified ecosystem; not directly imported in JS but legitimately listed as a runtime dep for TS consumers. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 2 / 8 | |
| 6.0.0 | 3 / 8 | |
| 5.1.0 | 4 / 10 | |
| 5.0.0 | 4 / 10 | |
| 2.1.0 | 3 / 7 | |
| 2.0.1 | 5 / 7 | |
| 2.0.0 | 5 / 11 | |
| 1.4.0 | 0 / 14 | |
| 1.3.1 | 0 / 14 | |
| 1.2.0 | 0 / 14 | |
| 1.1.2 | 0 / 14 | |
| 1.1.1 | 0 / 14 | |
| 1.1.0 | 0 / 14 | |
| 1.0.1 | 0 / 14 | |
| 1.0.0 | 0 / 16 |
v6.0.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.