@sctg/tracespace-cli
Render a PCB as SVGs from the command line
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pcb-stackup | AI (dependencies): Core PCB rendering dep; expected for a gerber-to-SVG CLI tool. | ai | |
| dependencies | unvetted-dep:gerber-to-svg | AI (dependencies): Core gerber rendering dep; expected for this package's purpose. | ai | |
| dependencies | unvetted-dep:whats-that-gerber | AI (dependencies): Gerber file detection utility; expected for this package's purpose. | ai | |
| dependencies | unvetted-dep:common-prefix | AI (dependencies): common-prefix is a benign string-utility package; no malicious history, stable use in this CLI tool. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.1.6 | 13 / 0 | |
| 5.1.5 | 13 / 0 | |
| 5.1.4 | 13 / 0 | |
| 5.1.3 | 13 / 0 | |
| 5.1.2 | 13 / 0 | |
| 5.1.1 | 13 / 0 | |
| 5.1.0 | 13 / 0 | |
| 5.0.0 | 13 / 0 |
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.