@antseed/cli No license 35 versions

@antseed/cli

npm

Antseed Network CLI and Web Dashboard

35

Versions

—

License

No

Install Scripts

Missing

Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

shahafan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@antseed/provider-core	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:cli-table3	AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package.	ai	2026/07/15
phantom-deps	phantom-dep:@antseed/node	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:@antseed/payments	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:@antseed/ant-agent	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:@antseed/dashboard	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:@antseed/api-adapter	AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive.	ai	2026/07/15
phantom-deps	phantom-dep:ora	AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package.	ai	2026/07/15
phantom-deps	phantom-dep:chalk	AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package.	ai	2026/07/15
phantom-deps	phantom-dep:dotenv	AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package.	ai	2026/07/15
phantom-deps	phantom-dep:commander	AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package.	ai	2026/07/15
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): Localhost RPC endpoint for local blockchain dev, not exfiltration.	ai	2026/07/15
dependencies	unvetted-dep:antseed-dashboard	AI (dependencies): Monorepo workspace dependency, not third-party.	ai	2026/07/15
dependencies	unvetted-dep:@antseed/dashboard	AI (dependencies): Sibling package in same monorepo/org, not third-party unvetted code.	ai	2026/07/15
provenance	missing-githead	AI (provenance): Publish env variance, no behavioral evidence; track record is clean.	ai	2026/07/15
phantom-deps	phantom-dep:open	AI (phantom-deps): 'open' is declared as a runtime dependency in package.json and used by the CLI; phantom-dep heuristic misfires here.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): @antseed/cli is a scoped CLI package for the Antseed Network project, not a typosquat of joi.	ai	2026/04/29

Versions (showing 35 of 135)

Version	Deps	Published
0.1.35	11 / 3	2026-03-15
0.1.34	11 / 3	2026-03-15
0.1.33	11 / 3	2026-03-15
0.1.32	11 / 3	2026-03-15
0.1.31	10 / 3	2026-03-14
0.1.30	9 / 3	2026-03-13
0.1.29	9 / 3	2026-03-13
0.1.28	9 / 3	2026-03-13
0.1.27	9 / 3	2026-03-13
0.1.26	9 / 3	2026-03-13
0.1.25	9 / 3	2026-03-10
0.1.24	9 / 3	2026-03-09
0.1.23	9 / 3	2026-03-05
0.1.22	9 / 3	2026-03-05
0.1.21	9 / 3	2026-03-02
0.1.20	8 / 3	2026-03-02
0.1.19	8 / 3	2026-03-01
0.1.18	8 / 3	2026-03-01
0.1.17	8 / 3	2026-03-01
0.1.16	8 / 3	2026-03-01
0.1.15	8 / 3	2026-03-01
0.1.14	8 / 3	2026-03-01
0.1.13	8 / 3	2026-02-28
0.1.12	8 / 3	2026-02-28
0.1.11	8 / 3	2026-02-27
0.1.10	8 / 3	2026-02-27
0.1.9	8 / 3	2026-02-27
0.1.8	8 / 3	2026-02-27
0.1.6	8 / 3	2026-02-27
0.1.5	8 / 3	2026-02-27
0.1.4	8 / 3	2026-02-26
0.1.3	8 / 3	2026-02-25
0.1.2	8 / 3	2026-02-25
0.1.1	8 / 3	2026-02-25
0.1.0	8 / 3	2026-02-24

v0.1.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.

v0.1.34

1 finding

LOW No provenance attestation provenance

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

v0.1.33

1 finding

LOW No provenance attestation provenance

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

v0.1.32

1 finding

LOW No provenance attestation provenance

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

v0.1.31

1 finding

LOW No provenance attestation provenance

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

v0.1.30

1 finding

LOW No provenance attestation provenance

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

v0.1.29

1 finding

LOW No provenance attestation provenance

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

v0.1.28

1 finding

LOW No provenance attestation provenance

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

v0.1.27

1 finding

LOW No provenance attestation provenance

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

v0.1.26

1 finding

LOW No provenance attestation provenance

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

v0.1.25

1 finding

LOW No provenance attestation provenance

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

v0.1.24

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.23

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.22

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.21

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.20

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.19

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.18

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.15

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.14

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.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.

v0.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.

v0.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.

v0.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.

v0.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.