@antseed/cli
Antseed Network CLI and Web Dashboard
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@antseed/provider-core | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:cli-table3 | AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@antseed/node | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@antseed/payments | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@antseed/ant-agent | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@antseed/dashboard | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@antseed/api-adapter | AI (phantom-deps): Org-scoped internal dependency used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI dependency used indirectly; stable false positive for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Localhost RPC endpoint for local blockchain dev, not exfiltration. | ai | |
| dependencies | unvetted-dep:antseed-dashboard | AI (dependencies): Monorepo workspace dependency, not third-party. | ai | |
| dependencies | unvetted-dep:@antseed/dashboard | AI (dependencies): Sibling package in same monorepo/org, not third-party unvetted code. | ai | |
| provenance | missing-githead | AI (provenance): Publish env variance, no behavioral evidence; track record is clean. | ai | |
| 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 | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @antseed/cli is a scoped CLI package for the Antseed Network project, not a typosquat of joi. | ai |
Versions (showing 51 of 135)
| Version | Deps | Published |
|---|---|---|
| 0.1.136 | 13 / 3 | |
| 0.1.135 | 13 / 3 | |
| 0.1.134 | 13 / 3 | |
| 0.1.133 | 13 / 3 | |
| 0.1.132 | 11 / 3 | |
| 0.1.131 | 11 / 3 | |
| 0.1.130 | 11 / 3 | |
| 0.1.129 | 11 / 3 | |
| 0.1.128 | 11 / 3 | |
| 0.1.127 | 11 / 3 | |
| 0.1.126 | 11 / 3 | |
| 0.1.125 | 11 / 3 | |
| 0.1.124 | 11 / 3 | |
| 0.1.123 | 11 / 3 | |
| 0.1.122 | 11 / 3 | |
| 0.1.121 | 11 / 3 | |
| 0.1.120 | 11 / 3 | |
| 0.1.119 | 11 / 3 | |
| 0.1.118 | 11 / 3 | |
| 0.1.117 | 11 / 3 | |
| 0.1.116 | 11 / 3 | |
| 0.1.115 | 11 / 3 | |
| 0.1.114 | 11 / 3 | |
| 0.1.113 | 11 / 3 | |
| 0.1.112 | 11 / 3 | |
| 0.1.111 | 11 / 3 | |
| 0.1.110 | 11 / 3 | |
| 0.1.109 | 11 / 3 | |
| 0.1.108 | 11 / 3 | |
| 0.1.107 | 11 / 3 | |
| 0.1.106 | 11 / 3 | |
| 0.1.105 | 11 / 3 | |
| 0.1.104 | 11 / 3 | |
| 0.1.103 | 11 / 3 | |
| 0.1.102 | 11 / 3 | |
| 0.1.101 | 11 / 3 | |
| 0.1.100 | 11 / 3 | |
| 0.1.99 | 11 / 3 | |
| 0.1.98 | 11 / 3 | |
| 0.1.97 | 11 / 3 | |
| 0.1.96 | 11 / 3 | |
| 0.1.95 | 11 / 3 | |
| 0.1.94 | 11 / 3 | |
| 0.1.93 | 11 / 3 | |
| 0.1.92 | 11 / 3 | |
| 0.1.91 | 11 / 3 | |
| 0.1.90 | 11 / 3 | |
| 0.1.89 | 11 / 3 | |
| 0.1.87 | 11 / 3 | |
| 0.1.86 | 12 / 3 | |
| 0.1.85 | 12 / 3 |
v0.1.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.133
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.132
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shahafan.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.119
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.118
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.116
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.115
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.114
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.113
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.112
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.111
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.