← Home

vinyl-buffer

Convert streaming vinyl files to use buffers

3
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

phatedhughsk

Keywords

vinylgulpfriendlyconvertbufferstream

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): vinyl-buffer has been published at 0.0.0 for 12+ years with 181k weekly downloads. This is an intentional version choice by a trusted author, not a malicious throwaway package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this established package. ai
provenance publisher-changed AI (provenance): phated (Blaine Bublitz) is a core gulp ecosystem maintainer; transfer from hughsk is a known legitimate handoff. ai
maintainer-change maintainer-added AI (maintainer-change): phated added as maintainer is consistent with gulp ecosystem ownership consolidation. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by stable utility; publish was maintenance transfer with no code changes. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.1 2 / 2
1.0.0 2 / 2
0.0.0 2 / 2

v1.0.1

2 findings
HIGH Publisher changed: hughsk → phated (on 2017-12-23) provenance

This version was published by a different npm account than previous versions on 2017-12-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

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