@squidcloud/cli
The Squid CLI
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @squidcloud org package; no provenance is consistent across all their releases. | ai | |
| phantom-deps | phantom-dep:@squidcloud/local-backend | AI (phantom-deps): Same-org scoped dep; used as a runtime peer, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:logpipes | AI (phantom-deps): CLI tool dependency referenced via config/spawn; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:nodemon | AI (phantom-deps): Used as a CLI subprocess tool, not directly imported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Referenced in scripts for TypeScript execution; not directly imported in bundled output. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @squidcloud/cli bears no resemblance to 'joi'; levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:decompress | AI (phantom-deps): CLI utility dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tsconfig-paths | AI (phantom-deps): Used via ts-node register flag in scripts; not directly imported. | ai | |
| phantom-deps | phantom-dep:adm-zip | AI (phantom-deps): Archive utility dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-loader | AI (phantom-deps): Webpack loader; used via webpack config, not direct import. | ai |
Versions (showing 51 of 170)
| Version | Deps | Published |
|---|---|---|
| 1.0.482 | 13 / 4 | |
| 1.0.481 | 13 / 4 | |
| 1.0.479 | 13 / 4 | |
| 1.0.478 | 13 / 4 | |
| 1.0.477 | 13 / 4 | |
| 1.0.476 | 13 / 4 | |
| 1.0.475 | 13 / 4 | |
| 1.0.474 | 13 / 4 | |
| 1.0.473 | 13 / 4 | |
| 1.0.472 | 13 / 4 | |
| 1.0.471 | 13 / 4 | |
| 1.0.470 | 13 / 4 | |
| 1.0.469 | 13 / 4 | |
| 1.0.468 | 13 / 4 | |
| 1.0.467 | 13 / 4 | |
| 1.0.466 | 13 / 4 | |
| 1.0.465 | 13 / 4 | |
| 1.0.462 | 13 / 4 | |
| 1.0.461 | 13 / 4 | |
| 1.0.457 | 13 / 4 | |
| 1.0.452 | 13 / 4 | |
| 1.0.447 | 12 / 4 | |
| 1.0.440 | 12 / 4 | |
| 1.0.426 | 12 / 4 | |
| 1.0.421 | 12 / 4 | |
| 1.0.419 | 12 / 4 | |
| 1.0.416 | 12 / 4 | |
| 1.0.415 | 12 / 4 | |
| 1.0.414 | 9 / 7 | |
| 1.0.413 | 12 / 4 | |
| 1.0.410 | 11 / 3 | |
| 1.0.392 | 11 / 3 | |
| 1.0.380 | 11 / 3 | |
| 1.0.379 | 11 / 3 | |
| 1.0.368 | 11 / 3 | |
| 1.0.366 | 11 / 3 | |
| 1.0.365 | 11 / 3 | |
| 1.0.357 | 11 / 3 | |
| 1.0.356 | 11 / 3 | |
| 1.0.355 | 11 / 3 | |
| 1.0.354 | 11 / 3 | |
| 1.0.353 | 11 / 3 | |
| 1.0.352 | 11 / 3 | |
| 1.0.351 | 11 / 3 | |
| 1.0.350 | 11 / 3 | |
| 1.0.349 | 11 / 3 | |
| 1.0.348 | 11 / 3 | |
| 1.0.347 | 11 / 3 | |
| 1.0.346 | 11 / 3 | |
| 1.0.345 | 11 / 3 | |
| 1.0.344 | 11 / 3 |
v1.0.482
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mfursov) than the most recent previously approved version (robbert_squid) on 2026-07-17, but mfursov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.481
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robbert_squid) than the most recent previously approved version (mfursov) on 2026-07-15, but robbert_squid is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.479
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wynnch-squid-ai) than the most recent previously approved version (mfursov) on 2026-07-13, but wynnch-squid-ai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.478
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2026-07-12, but mfursov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.477
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.476
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.475
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.474
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (squid.cloud) than the most recent previously approved version (victor-at-squid) on 2026-06-30, but squid.cloud is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.352
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.351
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.350
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.349
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.348
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.347
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.346
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.345
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.344
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.