← Home

@squidcloud/cli

npm

The Squid CLI

100
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tsouza-squidmfursovsquid.cloudwynnch-squid-aiyossisquidetaiatsquidrobbert_squidvictor-at-squid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 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
1.0.343 11 / 3
1.0.342 11 / 3
1.0.341 11 / 3
1.0.340 11 / 3
1.0.339 11 / 3
1.0.338 11 / 3
1.0.337 11 / 3
1.0.336 11 / 3
1.0.335 11 / 3
1.0.334 11 / 3
1.0.333 11 / 3
1.0.332 11 / 3
1.0.331 11 / 3
1.0.330 11 / 3
1.0.329 10 / 3
1.0.328 11 / 3
1.0.327 11 / 3
1.0.326 11 / 3
1.0.325 11 / 3
1.0.324 11 / 3
1.0.323 11 / 3
1.0.322 11 / 3
1.0.321 11 / 3
1.0.320 11 / 3
1.0.319 11 / 3
1.0.318 11 / 3
1.0.317 11 / 3
1.0.316 11 / 3
1.0.315 11 / 3
1.0.314 11 / 3
1.0.313 11 / 3
1.0.312 11 / 3
1.0.311 11 / 3
1.0.310 11 / 3
1.0.309 11 / 3
1.0.308 11 / 3
1.0.307 11 / 3
1.0.306 11 / 3
1.0.305 11 / 3
1.0.304 11 / 3
1.0.303 11 / 3
1.0.302 11 / 3
1.0.301 11 / 3
1.0.300 11 / 3
1.0.299 11 / 3
1.0.298 11 / 3
1.0.297 11 / 3
1.0.296 11 / 3
1.0.295 11 / 3
Showing 100 of 170 Next page →

v1.0.482

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: robbert_squid → mfursov (on 2026-07-17, known maintainer) provenance

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
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → robbert_squid (on 2026-07-15, known maintainer) provenance

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
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → wynnch-squid-ai (on 2026-07-13, known maintainer) provenance

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
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → mfursov (on 2026-07-12, known maintainer) provenance

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
INFO No provenance attestation provenance

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

v1.0.476

1 finding
INFO No provenance attestation provenance

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

v1.0.475

1 finding
INFO No provenance attestation provenance

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

v1.0.474

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → squid.cloud (on 2026-06-30, known maintainer) provenance

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
INFO No provenance attestation provenance

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

v1.0.351

1 finding
INFO No provenance attestation provenance

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

v1.0.350

1 finding
INFO No provenance attestation provenance

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

v1.0.349

1 finding
INFO No provenance attestation provenance

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

v1.0.348

1 finding
INFO No provenance attestation provenance

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

v1.0.347

1 finding
INFO No provenance attestation provenance

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

v1.0.346

1 finding
INFO No provenance attestation provenance

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

v1.0.345

1 finding
INFO No provenance attestation provenance

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

v1.0.344

1 finding
INFO No provenance attestation provenance

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

v1.0.343

1 finding
INFO No provenance attestation provenance

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

v1.0.342

1 finding
INFO No provenance attestation provenance

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

v1.0.341

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2025-03-27, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2025-03-27, 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.340

1 finding
INFO No provenance attestation provenance

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

v1.0.339

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → mfursov (on 2025-03-27, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2025-03-27, 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.338

1 finding
INFO No provenance attestation provenance

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

v1.0.337

1 finding
INFO No provenance attestation provenance

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

v1.0.336

1 finding
INFO No provenance attestation provenance

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

v1.0.335

1 finding
INFO No provenance attestation provenance

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

v1.0.334

1 finding
INFO No provenance attestation provenance

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

v1.0.333

1 finding
INFO No provenance attestation provenance

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

v1.0.332

1 finding
INFO No provenance attestation provenance

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

v1.0.331

1 finding
INFO No provenance attestation provenance

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

v1.0.330

1 finding
INFO No provenance attestation provenance

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

v1.0.329

1 finding
INFO No provenance attestation provenance

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

v1.0.328

1 finding
INFO No provenance attestation provenance

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

v1.0.327

1 finding
INFO No provenance attestation provenance

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

v1.0.326

1 finding
INFO No provenance attestation provenance

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

v1.0.325

1 finding
INFO No provenance attestation provenance

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

v1.0.324

1 finding
INFO No provenance attestation provenance

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

v1.0.323

1 finding
INFO No provenance attestation provenance

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

v1.0.322

1 finding
INFO No provenance attestation provenance

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

v1.0.321

1 finding
INFO No provenance attestation provenance

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

v1.0.320

1 finding
INFO No provenance attestation provenance

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

v1.0.319

1 finding
INFO No provenance attestation provenance

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

v1.0.318

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2025-02-24, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2025-02-24, 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.317

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → mfursov (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2025-02-20, 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.316

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2025-02-19, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2025-02-19, 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.315

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → mfursov (on 2025-02-19, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2025-02-19, 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.314

1 finding
INFO No provenance attestation provenance

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

v1.0.313

1 finding
INFO No provenance attestation provenance

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

v1.0.312

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: ohsnapitscolin → squid.cloud (on 2025-02-03, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (ohsnapitscolin) on 2025-02-03, 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.311

1 finding
INFO No provenance attestation provenance

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

v1.0.310

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → ohsnapitscolin (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (ohsnapitscolin) than the most recent previously approved version (squid.cloud) on 2025-01-29, but ohsnapitscolin 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.309

1 finding
INFO No provenance attestation provenance

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

v1.0.308

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: ohsnapitscolin → squid.cloud (on 2025-01-20, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (ohsnapitscolin) on 2025-01-20, 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.307

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → ohsnapitscolin (on 2025-01-14, known maintainer) provenance

This version was published by a different npm account (ohsnapitscolin) than the most recent previously approved version (squid.cloud) on 2025-01-14, but ohsnapitscolin 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.306

1 finding
INFO No provenance attestation provenance

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

v1.0.305

1 finding
INFO No provenance attestation provenance

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

v1.0.304

1 finding
INFO No provenance attestation provenance

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

v1.0.303

1 finding
INFO No provenance attestation provenance

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

v1.0.302

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2024-12-21, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2024-12-21, 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.301

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2024-12-18, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2024-12-18, 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.300

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → mfursov (on 2024-12-16, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2024-12-16, 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.299

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → squid.cloud (on 2024-11-27, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (mfursov) on 2024-11-27, 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.298

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: yossisquid → mfursov (on 2024-11-26, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (yossisquid) on 2024-11-26, 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.297

1 finding
INFO No provenance attestation provenance

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

v1.0.296

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: mfursov → yossisquid (on 2024-11-22, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (mfursov) on 2024-11-22, but yossisquid 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.295

1 finding
INFO No provenance attestation provenance

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