← Home

@embedder/embedder

npm Repository Homepage

AI-powered embedded systems development tool

51
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

imbobwei

Keywords

embedderaiembeddedclidevelopment

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@serialport/bindings-cpp AI (phantom-deps): Declared runtime dep likely bundled; stable false positive for this package. ai
phantom-deps phantom-dep:signal-exit AI (phantom-deps): Declared runtime dep likely bundled; stable false positive for this package. ai
phantom-deps phantom-dep:@sentry/node AI (phantom-deps): Declared runtime dep likely bundled; stable false positive for this package. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool for embedded hardware; child_process use in bundled output is expected for system interaction. ai
phantom-deps phantom-dep:@sentry/react AI (phantom-deps): Declared runtime dep likely bundled; stable false positive for this package. ai
phantom-deps phantom-dep:@serialport/stream AI (phantom-deps): Declared runtime dep likely bundled; stable false positive for this package. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall selects platform binary from optional deps; standard pattern for cross-platform CLI tools, stable across versions. ai

Versions (showing 51 of 64)

View all versions
Version Deps Published
3.0.12 0 / 0
3.0.10 0 / 0
3.0.7 0 / 0
3.0.3 0 / 0
3.0.0 0 / 0
2.1.17 5 / 0
2.1.16 5 / 0
2.1.15 5 / 0
2.1.14 5 / 0
2.1.13 5 / 0
2.1.12 5 / 0
2.1.11 5 / 0
2.1.10 5 / 0
2.1.9 5 / 0
2.1.8 5 / 0
2.1.7 5 / 0
2.1.6 5 / 0
2.1.5 5 / 0
2.1.4 5 / 0
2.1.3 5 / 0
2.1.2 5 / 0
2.1.1 5 / 0
2.1.0 5 / 0
2.0.37 5 / 0
2.0.36 5 / 0
2.0.35 5 / 0
2.0.34 5 / 0
2.0.33 5 / 0
0.3.113 0 / 0
0.3.111 0 / 0
0.3.106 0 / 0
0.3.105 0 / 0
0.3.97 0 / 0
0.3.96 0 / 0
0.3.94 0 / 0
0.3.93 0 / 0
0.3.92 0 / 0
0.3.88 0 / 0
0.3.87 0 / 0
0.3.86 0 / 0
0.3.85 0 / 0
0.3.84 0 / 0
0.3.81 0 / 0
0.3.80 0 / 0
0.3.73 0 / 0
0.3.69 0 / 0
0.3.67 0 / 0
0.3.64 0 / 0
0.3.58 0 / 0
0.3.56 0 / 0
0.3.54 0 / 0

v3.0.12

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.10

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.7

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.113

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.111

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.106

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.105

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.96

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.94

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.93

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.92

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.88

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.87

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.86

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.85

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.84

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.81

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.80

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.73

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.69

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.67

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.64

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.58

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.56

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.54

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node ./postinstall.mjs

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.