@tscircuit/schematic-viewer
React component for viewing [Circuit JSON](https://github.com/tscircuit/circuit-json) or tscircuit as a schematic
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64 blob is a bundled web worker for SPICE simulation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:performance-now | AI (phantom-deps): performance-now is a declared runtime dependency; phantom-dep heuristic false positive. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 2.0.74 | 4 / 15 | |
| 2.0.73 | 4 / 15 | |
| 2.0.72 | 4 / 15 | |
| 2.0.71 | 4 / 15 | |
| 2.0.70 | 4 / 15 | |
| 2.0.69 | 6 / 16 | |
| 2.0.68 | 6 / 16 | |
| 2.0.67 | 5 / 16 | |
| 2.0.66 | 6 / 16 | |
| 2.0.65 | 6 / 16 | |
| 2.0.64 | 6 / 16 | |
| 2.0.63 | 6 / 16 | |
| 2.0.62 | 6 / 16 | |
| 2.0.61 | 6 / 16 | |
| 2.0.60 | 6 / 16 | |
| 2.0.59 | 6 / 16 | |
| 2.0.58 | 6 / 16 | |
| 2.0.57 | 6 / 16 | |
| 2.0.56 | 6 / 16 | |
| 2.0.55 | 6 / 16 | |
| 2.0.54 | 6 / 16 | |
| 2.0.53 | 6 / 16 | |
| 2.0.52 | 6 / 16 | |
| 2.0.51 | 6 / 16 | |
| 2.0.50 | 6 / 16 | |
| 2.0.49 | 6 / 16 | |
| 2.0.48 | 6 / 16 | |
| 2.0.47 | 6 / 16 | |
| 2.0.46 | 6 / 16 | |
| 2.0.45 | 6 / 16 | |
| 2.0.44 | 6 / 16 | |
| 2.0.43 | 6 / 16 | |
| 2.0.42 | 6 / 16 | |
| 2.0.41 | 6 / 16 | |
| 2.0.40 | 6 / 16 | |
| 2.0.39 | 6 / 16 | |
| 2.0.38 | 6 / 16 | |
| 2.0.37 | 6 / 16 | |
| 2.0.36 | 6 / 16 | |
| 2.0.35 | 6 / 16 | |
| 2.0.34 | 6 / 16 | |
| 2.0.33 | 6 / 16 | |
| 2.0.32 | 6 / 16 | |
| 2.0.31 | 6 / 16 | |
| 2.0.30 | 6 / 15 | |
| 2.0.29 | 6 / 15 | |
| 2.0.28 | 6 / 15 | |
| 2.0.27 | 6 / 15 | |
| 2.0.26 | 6 / 15 | |
| 2.0.25 | 6 / 15 | |
| 2.0.24 | 3 / 17 | |
| 2.0.23 | 3 / 17 | |
| 2.0.22 | 3 / 17 | |
| 2.0.21 | 3 / 17 | |
| 2.0.20 | 3 / 17 | |
| 2.0.19 | 3 / 17 | |
| 2.0.18 | 3 / 17 | |
| 2.0.17 | 3 / 17 | |
| 2.0.16 | 3 / 17 | |
| 2.0.15 | 3 / 17 | |
| 2.0.14 | 3 / 17 | |
| 2.0.13 | 3 / 17 | |
| 2.0.12 | 3 / 17 | |
| 2.0.11 | 3 / 17 | |
| 2.0.10 | 3 / 17 | |
| 2.0.9 | 3 / 17 | |
| 2.0.8 | 3 / 16 | |
| 2.0.7 | 3 / 16 | |
| 2.0.6 | 5 / 14 | |
| 2.0.5 | 5 / 14 | |
| 2.0.4 | 4 / 14 | |
| 2.0.3 | 4 / 14 | |
| 2.0.2 | 4 / 14 | |
| 2.0.1 | 4 / 14 | |
| 2.0.0 | 4 / 14 |
v2.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.