@thescaffold/jsx-polylog
- Browser - Node.js (Javascript/Typescript)
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 228 days old with 18 versions and 30 approved dependents; 0.0.0 is a stable versioning choice for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is declared in package.json; phantom-dep heuristic fires but dep is intentionally included. | ai | |
| phantom-deps | phantom-dep:eventemitter2 | AI (phantom-deps): eventemitter2 is declared in package.json; phantom-dep heuristic fires but dep is intentionally included. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.2.46 | 3 / 0 | |
| 0.2.45 | 3 / 0 | |
| 0.2.43 | 3 / 0 | |
| 0.2.39 | 3 / 0 | |
| 0.2.38 | 3 / 0 | |
| 0.2.37 | 3 / 0 | |
| 0.2.35 | 3 / 0 | |
| 0.2.34 | 3 / 0 | |
| 0.2.33 | 3 / 0 | |
| 0.2.32 | 3 / 0 | |
| 0.2.31 | 3 / 0 | |
| 0.2.30 | 3 / 0 | |
| 0.2.21 | 3 / 0 | |
| 0.2.20 | 3 / 0 | |
| 0.0.10 | 3 / 0 | |
| 0.0.6 | 3 / 0 | |
| 0.0.5 | 3 / 0 | |
| 0.0.2 | 3 / 0 | |
| 0.0.0 | 3 / 0 |
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isaiahiroko.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.