easyeda
Convert EasyEDA JSON PCB footprints into [Circuit JSON](https://github.com/tscircuit/circuit-json) or tscircuit components.
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 | obfuscated-file:dist/index.js | AI (source-diff): Bundled library entrypoint from tsup build, matches build script change. | ai | |
| phantom-deps | phantom-dep:@tscircuit/mm | AI (phantom-deps): Declared in dependencies; used in build; stable false positive. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared in dependencies; used in build/CLI; stable false positive. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Declared in dependencies; used in CLI; stable false positive. | ai | |
| phantom-deps | phantom-dep:transformation-matrix | AI (phantom-deps): Declared in dependencies; used in build; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/main.cjs | AI (source-diff): Bundler-generated CJS output from tsup build, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected from adding bundled dist/browser and sourcemaps via new build scripts. | ai | |
| phantom-deps | phantom-dep:easyeda | AI (phantom-deps): Self-referential package name dep, not a real import concern. | ai |
Versions (showing 51 of 220)
| Version | Deps | Published |
|---|---|---|
| 0.0.277 | 0 / 15 | |
| 0.0.276 | 0 / 15 | |
| 0.0.275 | 0 / 15 | |
| 0.0.274 | 0 / 15 | |
| 0.0.273 | 0 / 15 | |
| 0.0.272 | 0 / 15 | |
| 0.0.271 | 0 / 14 | |
| 0.0.270 | 0 / 14 | |
| 0.0.269 | 0 / 14 | |
| 0.0.268 | 0 / 14 | |
| 0.0.267 | 0 / 14 | |
| 0.0.266 | 0 / 14 | |
| 0.0.265 | 0 / 14 | |
| 0.0.264 | 0 / 14 | |
| 0.0.263 | 0 / 13 | |
| 0.0.262 | 0 / 13 | |
| 0.0.261 | 0 / 13 | |
| 0.0.260 | 0 / 13 | |
| 0.0.259 | 0 / 13 | |
| 0.0.258 | 0 / 13 | |
| 0.0.257 | 0 / 13 | |
| 0.0.256 | 0 / 13 | |
| 0.0.255 | 0 / 13 | |
| 0.0.254 | 0 / 13 | |
| 0.0.253 | 0 / 13 | |
| 0.0.252 | 0 / 13 | |
| 0.0.251 | 0 / 13 | |
| 0.0.250 | 0 / 13 | |
| 0.0.248 | 0 / 11 | |
| 0.0.247 | 0 / 11 | |
| 0.0.242 | 0 / 12 | |
| 0.0.241 | 0 / 12 | |
| 0.0.240 | 0 / 12 | |
| 0.0.239 | 0 / 12 | |
| 0.0.238 | 0 / 12 | |
| 0.0.237 | 0 / 12 | |
| 0.0.236 | 1 / 12 | |
| 0.0.235 | 1 / 11 | |
| 0.0.234 | 0 / 11 | |
| 0.0.233 | 0 / 11 | |
| 0.0.232 | 0 / 10 | |
| 0.0.231 | 0 / 10 | |
| 0.0.230 | 0 / 10 | |
| 0.0.229 | 0 / 10 | |
| 0.0.198 | 6 / 8 | |
| 0.0.197 | 6 / 8 | |
| 0.0.196 | 5 / 9 | |
| 0.0.195 | 5 / 9 | |
| 0.0.194 | 5 / 9 | |
| 0.0.193 | 5 / 9 | |
| 0.0.192 | 5 / 9 |
v0.0.277
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.248
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.247
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.242
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.241
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.233
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.232
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.231
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.230
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.229
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.