@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 — 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 |
|---|---|---|---|---|
| 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 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.0.467
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.466
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.465
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 (victor-at-squid) than the most recent previously approved version (squid.cloud) on 2026-05-26, but victor-at-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.462
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.461
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.457
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.452
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.447
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.440
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.421
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.419
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.416
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.415
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.414
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.413
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.410
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.392
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.380
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.379
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.368
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.366
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.365
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.357
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.356
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.355
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.354
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.353
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.