@antseed/node — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

shahafan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall runs a local patch script for ethers dependency; consistent with documented SDK purpose.	ai	2026/04/29
semgrep	semgrep:env-spread	AI (semgrep): env-spread in native module rebuild helper passing arch flags; standard pattern, not exfiltration.	ai	2026/04/29
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped package @antseed/node has no resemblance to zod in purpose or name; levenshtein match is spurious.	ai	2026/04/29

Versions (showing 3 of 3)

Version	Deps	Published
0.2.86	7 / 5	2026-05-17
0.2.74	7 / 5	2026-04-26
0.2.28	7 / 5	2026-04-05

v0.2.86

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.74

3 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/patch-ethers.js

HIGH env-spread: scripts/ensure-node-native-modules.mjs:130 semgrep

Spreading entire process.env into an object — may capture all secrets 128 | cwd: nodePackageDir, 129 | stdio: 'inherit', > 130 | env: { 131 | ...process.env, 132 | npm_config_arch: process.arch,

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.