← Home

@soundtouchjs/audio-worklet

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

cutterbl

Keywords

audioWebAudioAudioWorkletTypeScriptpitchtemposoundtouch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance confirms CI/CD publish; same maintainer/org resuming development after hiatus. ai
phantom-deps phantom-dep:@soundtouchjs/worklet-base AI (phantom-deps): Same org scope; likely re-exported or used indirectly as a peer/build dep within the monorepo. ai
provenance missing-githead AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor metadata gap, not a supply-chain risk. ai
phantom-deps phantom-dep:@soundtouchjs/core AI (phantom-deps): Same-org scoped dep; re-exported rather than directly imported in this monorepo package. ai
phantom-deps phantom-dep:@soundtouchjs/interpolation-strategy-lanczos AI (phantom-deps): Same-org monorepo dep; likely bundled into the dist output rather than directly imported in source. ai

Versions (showing 9 of 9)

Version Deps Published
2.0.4 3 / 0
2.0.1 2 / 0
1.0.8 1 / 0
1.0.6 1 / 0
1.0.4 1 / 0
1.0.3 1 / 0
1.0.2 1 / 0
1.0.0 1 / 0
0.3.0 0 / 22

v2.0.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.8

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cutterbl.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.6

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cutterbl.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cutterbl.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cutterbl.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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