circuit-json-to-kicad
Convert [Circuit JSON](https://github.com/tscircuit/circuit-json) files to KiCad schematic (`.kicad_sch`), PCB (`.kicad_pcb`), and project (`.kicad_pro`) files.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Early-stage tscircuit ecosystem package from a highly trusted publisher; sparse metadata is expected at v0.0.1. | ai | |
| dependencies | unvetted-dep:circuit-json | AI (dependencies): circuit-json is a first-party tscircuit ecosystem package directly relevant to this converter's core functionality; stable accept for this package. | ai | |
| dependencies | unvetted-dep:@tscircuit/props | AI (dependencies): @tscircuit/props is a first-party tscircuit ecosystem package from the same publisher org; directly relevant to circuit JSON processing. | ai |
Versions (showing 51 of 148)
| Version | Deps | Published |
|---|---|---|
| 0.0.149 | 0 / 9 | |
| 0.0.148 | 0 / 9 | |
| 0.0.147 | 0 / 9 | |
| 0.0.146 | 0 / 9 | |
| 0.0.145 | 0 / 9 | |
| 0.0.144 | 0 / 9 | |
| 0.0.143 | 0 / 9 | |
| 0.0.142 | 0 / 9 | |
| 0.0.141 | 0 / 9 | |
| 0.0.140 | 0 / 9 | |
| 0.0.139 | 0 / 9 | |
| 0.0.137 | 0 / 9 | |
| 0.0.136 | 0 / 9 | |
| 0.0.135 | 0 / 9 | |
| 0.0.134 | 0 / 9 | |
| 0.0.133 | 0 / 9 | |
| 0.0.132 | 0 / 9 | |
| 0.0.131 | 0 / 9 | |
| 0.0.130 | 0 / 9 | |
| 0.0.129 | 0 / 9 | |
| 0.0.128 | 0 / 9 | |
| 0.0.127 | 0 / 9 | |
| 0.0.126 | 0 / 9 | |
| 0.0.125 | 0 / 9 | |
| 0.0.124 | 0 / 9 | |
| 0.0.123 | 0 / 9 | |
| 0.0.122 | 0 / 9 | |
| 0.0.121 | 0 / 9 | |
| 0.0.120 | 0 / 9 | |
| 0.0.119 | 0 / 9 | |
| 0.0.118 | 0 / 9 | |
| 0.0.117 | 0 / 9 | |
| 0.0.116 | 0 / 9 | |
| 0.0.115 | 0 / 9 | |
| 0.0.114 | 0 / 9 | |
| 0.0.113 | 0 / 9 | |
| 0.0.112 | 0 / 9 | |
| 0.0.111 | 0 / 9 | |
| 0.0.110 | 0 / 9 | |
| 0.0.109 | 0 / 9 | |
| 0.0.108 | 0 / 9 | |
| 0.0.107 | 0 / 9 | |
| 0.0.106 | 0 / 9 | |
| 0.0.105 | 0 / 9 | |
| 0.0.104 | 0 / 9 | |
| 0.0.103 | 0 / 9 | |
| 0.0.102 | 0 / 9 | |
| 0.0.101 | 0 / 9 | |
| 0.0.100 | 0 / 9 | |
| 0.0.99 | 0 / 9 | |
| 0.0.98 | 0 / 9 |
v0.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.