@tscircuit/pcb-viewer
[](https://badge.fury.io/js/@tscircuit%2Fpcb-viewer)
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
Versions (showing 100 of 419)
| Version | Deps | Published |
|---|---|---|
| 1.11.167 | 12 / 27 | |
| 1.11.166 | 12 / 26 | |
| 1.11.165 | 12 / 26 | |
| 1.11.164 | 12 / 26 | |
| 1.11.163 | 11 / 26 | |
| 1.11.162 | 11 / 26 | |
| 1.11.161 | 11 / 26 | |
| 1.11.160 | 11 / 26 | |
| 1.11.159 | 11 / 26 | |
| 1.11.158 | 11 / 26 | |
| 1.11.157 | 11 / 26 | |
| 1.11.156 | 11 / 26 | |
| 1.11.155 | 11 / 26 | |
| 1.11.154 | 11 / 26 | |
| 1.11.153 | 11 / 26 | |
| 1.11.152 | 11 / 26 | |
| 1.11.151 | 11 / 26 | |
| 1.11.150 | 10 / 26 | |
| 1.11.149 | 10 / 26 | |
| 1.11.148 | 10 / 26 | |
| 1.11.147 | 10 / 26 | |
| 1.11.146 | 11 / 26 | |
| 1.11.145 | 11 / 26 | |
| 1.11.144 | 11 / 26 | |
| 1.11.143 | 11 / 26 | |
| 1.11.142 | 11 / 26 | |
| 1.11.141 | 11 / 26 | |
| 1.11.140 | 11 / 26 | |
| 1.11.139 | 11 / 26 | |
| 1.11.138 | 11 / 26 | |
| 1.11.137 | 11 / 26 | |
| 1.11.136 | 11 / 26 | |
| 1.11.135 | 11 / 26 | |
| 1.11.134 | 11 / 26 | |
| 1.11.133 | 11 / 26 | |
| 1.11.132 | 11 / 26 | |
| 1.11.131 | 11 / 26 | |
| 1.11.130 | 11 / 26 | |
| 1.11.129 | 11 / 26 | |
| 1.11.128 | 11 / 26 | |
| 1.11.127 | 11 / 26 | |
| 1.11.126 | 11 / 26 | |
| 1.11.125 | 11 / 26 | |
| 1.11.124 | 11 / 26 | |
| 1.11.123 | 11 / 26 | |
| 1.11.122 | 11 / 26 | |
| 1.11.121 | 11 / 26 | |
| 1.11.120 | 11 / 26 | |
| 1.11.119 | 11 / 26 | |
| 1.11.118 | 11 / 26 | |
| 1.11.117 | 11 / 26 | |
| 1.11.116 | 11 / 26 | |
| 1.11.115 | 11 / 26 | |
| 1.11.114 | 11 / 26 | |
| 1.11.113 | 11 / 26 | |
| 1.11.112 | 11 / 26 | |
| 1.11.111 | 11 / 26 | |
| 1.11.110 | 11 / 26 | |
| 1.11.109 | 10 / 27 | |
| 1.11.108 | 10 / 27 | |
| 1.11.107 | 10 / 27 | |
| 1.11.106 | 10 / 27 | |
| 1.11.105 | 10 / 27 | |
| 1.11.104 | 10 / 27 | |
| 1.11.103 | 10 / 27 | |
| 1.11.102 | 10 / 27 | |
| 1.11.101 | 10 / 27 | |
| 1.11.100 | 10 / 27 | |
| 1.11.99 | 10 / 27 | |
| 1.11.98 | 10 / 27 | |
| 1.11.97 | 10 / 27 | |
| 1.11.96 | 10 / 27 | |
| 1.11.95 | 10 / 27 | |
| 1.11.92 | 10 / 27 | |
| 1.11.91 | 10 / 27 | |
| 1.11.90 | 10 / 27 | |
| 1.11.89 | 10 / 27 | |
| 1.11.88 | 10 / 27 | |
| 1.11.87 | 10 / 27 | |
| 1.11.86 | 10 / 27 | |
| 1.11.85 | 10 / 27 | |
| 1.11.84 | 10 / 27 | |
| 1.11.83 | 10 / 27 | |
| 1.11.82 | 10 / 27 | |
| 1.11.81 | 10 / 27 | |
| 1.11.80 | 10 / 27 | |
| 1.11.79 | 10 / 27 | |
| 1.11.78 | 10 / 27 | |
| 1.11.77 | 10 / 27 | |
| 1.11.76 | 10 / 27 | |
| 1.11.75 | 10 / 27 | |
| 1.11.74 | 10 / 27 | |
| 1.11.73 | 10 / 27 | |
| 1.11.72 | 10 / 27 | |
| 1.11.71 | 10 / 27 | |
| 1.11.70 | 10 / 27 | |
| 1.11.69 | 10 / 27 | |
| 1.11.68 | 10 / 27 | |
| 1.11.67 | 10 / 27 | |
| 1.11.66 | 10 / 27 |
v1.11.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.