@pie-players/pie-players-shared
Shared runtime + UI utilities 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@sveltejs/kit | AI (phantom-deps): Framework-scoped package loaded by convention in SvelteKit projects, not directly imported. | ai | |
| phantom-deps | phantom-dep:daisyui | AI (phantom-deps): daisyui is a CSS/Tailwind plugin referenced in config, not a JS import; phantom-dep false positive for this package. | ai | |
| dependencies | unvetted-dep:@pie-players/math-renderer-core | AI (dependencies): Sibling workspace package in the same pie-framework monorepo; not an external dependency risk. | ai | |
| dependencies | unvetted-dep:@pie-players/math-renderer-mathjax | AI (dependencies): Sibling workspace package in the same pie-framework monorepo; not an external dependency risk. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.3.49 | 3 / 6 | |
| 0.3.48 | 3 / 6 | |
| 0.3.47 | 3 / 6 | |
| 0.3.46 | 3 / 6 | |
| 0.3.45 | 3 / 6 | |
| 0.3.44 | 3 / 6 | |
| 0.3.43 | 3 / 6 | |
| 0.3.42 | 3 / 6 | |
| 0.3.41 | 3 / 6 | |
| 0.3.40 | 3 / 6 | |
| 0.3.39 | 3 / 6 | |
| 0.3.38 | 4 / 5 | |
| 0.3.37 | 4 / 5 | |
| 0.3.36 | 4 / 5 | |
| 0.3.35 | 4 / 5 | |
| 0.3.34 | 4 / 5 | |
| 0.3.33 | 4 / 5 | |
| 0.3.32 | 4 / 5 | |
| 0.3.31 | 4 / 5 | |
| 0.3.30 | 4 / 5 | |
| 0.3.29 | 2 / 3 | |
| 0.3.28 | 2 / 3 | |
| 0.3.27 | 2 / 3 | |
| 0.3.26 | 2 / 3 | |
| 0.3.25 | 2 / 3 | |
| 0.3.24 | 2 / 3 | |
| 0.3.23 | 2 / 3 | |
| 0.3.22 | 2 / 3 | |
| 0.3.21 | 2 / 3 | |
| 0.3.20 | 2 / 3 | |
| 0.3.19 | 2 / 3 | |
| 0.3.17 | 2 / 3 | |
| 0.3.16 | 2 / 3 | |
| 0.3.13 | 2 / 3 | |
| 0.3.12 | 2 / 3 | |
| 0.3.11 | 2 / 3 | |
| 0.3.10 | 2 / 3 | |
| 0.3.9 | 2 / 3 | |
| 0.3.8 | 2 / 3 | |
| 0.3.7 | 2 / 3 | |
| 0.3.5 | 2 / 3 | |
| 0.3.4 | 2 / 3 | |
| 0.3.3 | 2 / 3 | |
| 0.3.2 | 3 / 3 | |
| 0.3.1 | 3 / 3 | |
| 0.3.0 | 3 / 3 | |
| 0.2.7 | 3 / 3 | |
| 0.2.6 | 3 / 3 | |
| 0.2.5 | 3 / 3 | |
| 0.2.4 | 4 / 3 | |
| 0.2.2 | 2 / 3 |
v0.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
2 findingsPackage 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 unknown date, 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
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.31
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.