@waveform-playlist/browser
Browser bundle for waveform-playlist with React
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:@waveform-playlist/core | AI (phantom-deps): Same-org monorepo sibling; re-exported via bundle rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/webaudio-peaks | AI (phantom-deps): Same-org monorepo dep; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/recording | AI (phantom-deps): Same-org monorepo dep; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/annotations | AI (phantom-deps): Same-org monorepo dep; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/ui-components | AI (phantom-deps): Same-org monorepo dep; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/playout | AI (phantom-deps): Same-org monorepo dep; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| provenance | no-provenance | AI (provenance): Established open-source monorepo; lack of provenance is common and not indicative of risk here. | ai | |
| phantom-deps | phantom-dep:@waveform-playlist/loaders | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is unreliable for monorepo packages re-exported via bundle. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic fires but it may be used indirectly via bundled output. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 13.0.0 | 9 / 6 | |
| 12.1.0 | 9 / 6 | |
| 12.0.0 | 9 / 6 | |
| 11.3.1 | 9 / 6 | |
| 11.3.0 | 9 / 6 | |
| 11.2.0 | 9 / 6 | |
| 11.1.0 | 9 / 6 | |
| 11.0.1 | 9 / 6 | |
| 11.0.0 | 9 / 6 | |
| 10.4.0 | 9 / 6 | |
| 10.3.0 | 9 / 6 | |
| 10.2.0 | 9 / 6 | |
| 10.1.2 | 9 / 6 | |
| 9.2.1 | 8 / 8 | |
| 9.1.2 | 8 / 8 | |
| 7.1.3 | 7 / 7 | |
| 7.1.2 | 7 / 7 | |
| 7.1.1 | 7 / 7 | |
| 7.1.0 | 7 / 7 | |
| 5.0.0 | 10 / 7 |
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
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.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.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.
v7.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.
v7.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.