@pie-players/pie-toolbars
Item and section toolbar custom elements for PIE players
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:daisyui | AI (phantom-deps): CSS framework used in Svelte/Vite config/build, not directly imported in JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-context | AI (phantom-deps): Same-org dep likely consumed via Svelte components or re-exported; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-calculator-mathjs | AI (phantom-deps): Same-org dep; phantom detection is a false positive for this bundled Svelte package. | ai | |
| phantom-deps | phantom-dep:@pie-players/pie-default-tool-loaders | AI (phantom-deps): Same-org dep; phantom detection is a false positive for this bundled Svelte package. | ai | |
| provenance | no-provenance | AI (provenance): Established pie-framework monorepo package; lack of provenance is consistent across all versions. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.3.47 | 1 / 6 | |
| 0.3.46 | 1 / 6 | |
| 0.3.45 | 1 / 6 | |
| 0.3.44 | 1 / 6 | |
| 0.3.43 | 1 / 6 | |
| 0.3.42 | 1 / 6 | |
| 0.3.41 | 1 / 6 | |
| 0.3.40 | 1 / 6 | |
| 0.3.39 | 1 / 6 | |
| 0.3.38 | 1 / 6 | |
| 0.3.37 | 1 / 6 | |
| 0.3.36 | 1 / 6 | |
| 0.3.35 | 1 / 6 | |
| 0.3.34 | 1 / 6 | |
| 0.3.33 | 1 / 6 | |
| 0.3.32 | 1 / 6 | |
| 0.3.31 | 1 / 6 | |
| 0.3.30 | 1 / 6 | |
| 0.3.29 | 1 / 6 | |
| 0.3.28 | 1 / 6 | |
| 0.3.27 | 1 / 6 | |
| 0.3.26 | 1 / 6 | |
| 0.3.25 | 1 / 6 | |
| 0.3.24 | 1 / 6 | |
| 0.3.23 | 1 / 6 | |
| 0.3.22 | 1 / 6 | |
| 0.3.21 | 1 / 6 | |
| 0.3.20 | 1 / 6 | |
| 0.3.19 | 1 / 6 | |
| 0.3.17 | 1 / 6 | |
| 0.3.16 | 1 / 6 | |
| 0.3.13 | 1 / 6 | |
| 0.3.12 | 1 / 6 | |
| 0.3.11 | 1 / 6 | |
| 0.3.10 | 1 / 6 | |
| 0.3.9 | 1 / 6 | |
| 0.3.8 | 1 / 6 | |
| 0.3.7 | 1 / 6 | |
| 0.3.5 | 1 / 6 | |
| 0.3.4 | 1 / 6 | |
| 0.3.3 | 1 / 6 | |
| 0.3.2 | 1 / 6 | |
| 0.3.1 | 1 / 6 | |
| 0.1.2 | 5 / 6 | |
| 0.1.0 | 5 / 6 |
v0.3.47
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (carlacostea) than the most recent previously approved version (chillenious) on 2026-06-03, but carlacostea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.