@types/vinyl
TypeScript definitions for vinyl
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/node | AI (dependencies): @types/node is a standard DefinitelyTyped dependency used across all @types/* packages; not a security risk for this package. | ai | |
| dependencies | unvetted-dep:@types/expect | AI (dependencies): @types/expect is a standard DefinitelyTyped test dependency; not a security risk for this type-definition package. | ai | |
| email-domain | unclaimed-email:https://github.com/vvakame/ | AI (email-domain): The 'email' field is actually a GitHub profile URL, not an email address. The analyzer is misinterpreting the author field format used in older DefinitelyTyped packages. No real domain hijacking risk. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped @types packages published via the types bot do not include Sigstore provenance; this is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only packages like @types/node are loaded by TypeScript convention, not direct imports. This is expected behavior for all DefinitelyTyped packages. | ai | |
| phantom-deps | phantom-dep:@types/expect | AI (phantom-deps): Type-only packages like @types/expect are loaded by TypeScript convention, not direct imports. This is expected behavior for all DefinitelyTyped packages. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 2 / 0 | |
| 2.0.11 | 2 / 0 | |
| 2.0.10 | 2 / 0 | |
| 2.0.9 | 2 / 0 | |
| 2.0.8 | 2 / 0 | |
| 2.0.7 | 2 / 0 | |
| 2.0.6 | 2 / 0 | |
| 2.0.5 | 2 / 0 | |
| 2.0.4 | 2 / 0 | |
| 2.0.3 | 1 / 0 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.2.30 | 1 / 0 | |
| 1.1.29 | 1 / 0 | |
| 1.1.28 | 1 / 0 | |
| 1.1.27 | 1 / 0 | |
| 0.4.6 | 1 / 0 | |
| 0.4.5 | 1 / 0 | |
| 0.4.4 | 1 / 0 | |
| 0.4.3 | 1 / 0 | |
| 0.4.2 | 1 / 0 | |
| 0.4.1 | 1 / 0 | |
| 0.4.0 | 1 / 0 |
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.