@noego/wood
Declarative Electron desktop apps using the noego ecosystem.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Pattern is passing process.env to child_process spawn with one added var — standard CLI tool pattern, not exfiltration. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): IP is 127.0.0.1 (localhost debug port) — not a remote raw IP, clearly benign for a dev tool. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @noego/wood is an Electron/Svelte framework; no intent to impersonate zod. | ai | |
| phantom-deps | phantom-dep:@noego/stitch | AI (phantom-deps): Same-org dependency; may be used transitively or via config rather than direct import. | ai | |
| phantom-deps | phantom-dep:path-to-regexp | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 11 / 10 | |
| 0.4.2 | 11 / 10 | |
| 0.4.1 | 10 / 10 | |
| 0.4.0 | 10 / 10 | |
| 0.3.0 | 10 / 10 | |
| 0.2.1 | 10 / 10 | |
| 0.2.0 | 10 / 10 | |
| 0.1.3 | 10 / 9 | |
| 0.1.2 | 10 / 9 | |
| 0.1.1 | 10 / 9 | |
| 0.1.0 | 10 / 9 | |
| 0.0.4 | 10 / 9 | |
| 0.0.3 | 10 / 9 | |
| 0.0.1 | 10 / 9 |
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
3 findingsSpreading entire process.env into an object — may capture all secrets 25 | stdio: 'inherit', 26 | shell: true, > 27 | env: { ...process.env, STICK_CLI: '1' }, 28 | } 29 | );
Spreading entire process.env into an object — may capture all secrets 524 | shell: true, 525 | cwd: projectRoot, > 526 | env: { 527 | ...process.env, 528 | WOOD_MODE: modeEnv,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.