@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 70 of 170)
| Version | Deps | Published |
|---|---|---|
| 1.0.294 | 11 / 3 | |
| 1.0.293 | 11 / 3 | |
| 1.0.292 | 11 / 3 | |
| 1.0.291 | 11 / 3 | |
| 1.0.290 | 11 / 3 | |
| 1.0.289 | 11 / 3 | |
| 1.0.288 | 11 / 3 | |
| 1.0.287 | 11 / 3 | |
| 1.0.286 | 11 / 3 | |
| 1.0.285 | 11 / 3 | |
| 1.0.284 | 11 / 3 | |
| 1.0.283 | 11 / 3 | |
| 1.0.282 | 11 / 3 | |
| 1.0.281 | 11 / 3 | |
| 1.0.280 | 11 / 3 | |
| 1.0.279 | 11 / 3 | |
| 1.0.278 | 11 / 3 | |
| 1.0.277 | 11 / 3 | |
| 1.0.276 | 11 / 3 | |
| 1.0.275 | 11 / 3 | |
| 1.0.274 | 11 / 3 | |
| 1.0.273 | 11 / 3 | |
| 1.0.272 | 11 / 3 | |
| 1.0.271 | 11 / 3 | |
| 1.0.270 | 11 / 3 | |
| 1.0.269 | 11 / 3 | |
| 1.0.268 | 11 / 3 | |
| 1.0.267 | 11 / 3 | |
| 1.0.266 | 11 / 3 | |
| 1.0.265 | 11 / 3 | |
| 1.0.264 | 11 / 3 | |
| 1.0.263 | 11 / 3 | |
| 1.0.262 | 11 / 3 | |
| 1.0.261 | 11 / 3 | |
| 1.0.260 | 12 / 3 | |
| 1.0.259 | 12 / 3 | |
| 1.0.258 | 12 / 3 | |
| 1.0.257 | 12 / 3 | |
| 1.0.256 | 12 / 3 | |
| 1.0.255 | 12 / 3 | |
| 1.0.254 | 12 / 3 | |
| 1.0.253 | 12 / 3 | |
| 1.0.252 | 12 / 3 | |
| 1.0.251 | 12 / 3 | |
| 1.0.250 | 12 / 3 | |
| 1.0.249 | 12 / 3 | |
| 1.0.248 | 12 / 3 | |
| 1.0.247 | 12 / 3 | |
| 1.0.246 | 12 / 3 | |
| 1.0.245 | 12 / 3 | |
| 1.0.244 | 12 / 3 | |
| 1.0.243 | 12 / 2 | |
| 1.0.242 | 12 / 2 | |
| 1.0.241 | 12 / 2 | |
| 1.0.240 | 12 / 2 | |
| 1.0.239 | 12 / 2 | |
| 1.0.238 | 14 / 2 | |
| 1.0.237 | 14 / 2 | |
| 1.0.236 | 3 / 1 | |
| 1.0.235 | 3 / 1 | |
| 1.0.234 | 3 / 1 | |
| 1.0.233 | 3 / 1 | |
| 1.0.230 | 3 / 1 | |
| 1.0.229 | 3 / 1 | |
| 1.0.228 | 3 / 1 | |
| 1.0.227 | 3 / 1 | |
| 1.0.226 | 4 / 1 | |
| 1.0.225 | 4 / 1 | |
| 1.0.224 | 4 / 1 | |
| 1.0.223 | 4 / 1 |
v1.0.294
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 2024-11-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.293
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 2024-11-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.292
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 (mfursov) on 2024-11-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.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.288
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 2024-11-13, 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.287
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 2024-11-04, 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.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.283
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 (mfursov) on 2024-10-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.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.281
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 2024-10-03, 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.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
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 (ohsnapitscolin) on 2024-07-29, 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.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
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 (ohsnapitscolin) than the most recent previously approved version (mfursov) on 2024-07-24, 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.259
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 2024-07-24, 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.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.255
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 (mfursov) on 2024-07-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.254
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 2024-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.253
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.252
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.249
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 (mfursov) on 2024-07-08, 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.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.247
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 2024-07-02, 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.246
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 2024-07-01, 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.245
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 (mfursov) on 2024-06-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.244
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 2024-06-18, 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.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.242
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 2024-06-14, 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.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.240
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 (ohsnapitscolin) on 2024-06-12, 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.239
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.238
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.237
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.236
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.235
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.234
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.233
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.230
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.229
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.228
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.227
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.226
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.225
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.224
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.223
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.