← Home

@squidcloud/local-backend

npm
51
Versions
UNLICENSED
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
phantom-deps phantom-dep:tsoa AI (phantom-deps): tsoa is a declared runtime dep used via config/CLI, not direct import; stable FP for this package. ai
phantom-deps phantom-dep:express AI (phantom-deps): express is used via NestJS platform adapter, not direct import; stable FP. ai
phantom-deps phantom-dep:graphql AI (phantom-deps): graphql is a peer/runtime dep consumed indirectly; stable FP. ai
phantom-deps phantom-dep:json-schema-typed AI (phantom-deps): json-schema-typed used via tsoa config; stable FP. ai
phantom-deps phantom-dep:@nestjs/platform-express AI (phantom-deps): NestJS platform adapter registered via module config, not direct import; stable FP. ai

Versions (showing 51 of 360)

View all versions
Version Deps Published
1.0.483 16 / 7
1.0.482 16 / 7
1.0.481 16 / 7
1.0.479 16 / 7
1.0.478 16 / 7
1.0.477 16 / 7
1.0.476 16 / 7
1.0.475 16 / 7
1.0.474 16 / 7
1.0.473 16 / 7
1.0.472 16 / 7
1.0.471 16 / 7
1.0.470 16 / 7
1.0.469 16 / 7
1.0.468 16 / 7
1.0.467 16 / 7
1.0.466 16 / 7
1.0.465 16 / 7
1.0.464 16 / 7
1.0.463 16 / 7
1.0.462 16 / 7
1.0.461 16 / 7
1.0.460 16 / 7
1.0.459 16 / 7
1.0.458 16 / 7
1.0.457 16 / 7
1.0.456 16 / 7
1.0.455 16 / 7
1.0.454 16 / 7
1.0.453 16 / 7
1.0.452 16 / 7
1.0.449 14 / 7
1.0.447 14 / 7
1.0.446 14 / 7
1.0.445 14 / 7
1.0.444 14 / 7
1.0.443 14 / 7
1.0.442 14 / 7
1.0.441 14 / 7
1.0.440 14 / 7
1.0.439 14 / 7
1.0.438 14 / 7
1.0.437 14 / 7
1.0.436 14 / 7
1.0.435 14 / 7
1.0.434 14 / 7
1.0.433 14 / 7
1.0.432 14 / 7
1.0.431 14 / 7
1.0.430 14 / 7
1.0.429 14 / 7

v1.0.483

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (mfursov) than the most recent previously approved version (wynnch-squid-ai) on 2026-07-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.482

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wynnch-squid-ai → mfursov (on unknown date, known maintainer) provenance

This version was published by a different npm account (mfursov) than the most recent previously approved version (wynnch-squid-ai) on unknown date, 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
LOW No provenance attestation provenance

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

INFO Publisher changed: wynnch-squid-ai → robbert_squid (on unknown date, known maintainer) provenance

This version was published by a different npm account (robbert_squid) than the most recent previously approved version (wynnch-squid-ai) on unknown date, 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
LOW No provenance attestation provenance

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

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

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

v1.0.476

1 finding
LOW No provenance attestation provenance

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

v1.0.475

1 finding
LOW No provenance attestation provenance

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

v1.0.474

2 findings
LOW No provenance attestation provenance

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.473

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → victor-at-squid (on 2026-06-17, known maintainer) provenance

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (yossisquid) on 2026-06-17, 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.472

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → victor-at-squid (on 2026-06-12, known maintainer) provenance

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (yossisquid) on 2026-06-12, 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.471

1 finding
LOW No provenance attestation provenance

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

v1.0.470

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → victor-at-squid (on 2026-06-10, known maintainer) provenance

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (yossisquid) on 2026-06-10, 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.469

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → yossisquid (on 2026-06-09, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (victor-at-squid) on 2026-06-09, 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.468

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → yossisquid (on 2026-06-05, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (victor-at-squid) on 2026-06-05, 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.467

1 finding
LOW No provenance attestation provenance

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

v1.0.466

1 finding
LOW No provenance attestation provenance

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

v1.0.465

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mfursov → victor-at-squid (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (mfursov) 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.464

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2026-05-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.463

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (squid.cloud) on 2026-04-29, 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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → squid.cloud (on 2026-04-25, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (yossisquid) on 2026-04-25, 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.460

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → wynnch-squid-ai (on 2026-04-22, known maintainer) provenance

This version was published by a different npm account (wynnch-squid-ai) than the most recent previously approved version (victor-at-squid) on 2026-04-22, 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.457

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → yossisquid (on 2026-04-08, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (victor-at-squid) on 2026-04-08, 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.455

1 finding
LOW No provenance attestation provenance

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

v1.0.453

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → squid.cloud (on 2026-04-03, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (yossisquid) on 2026-04-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.449

2 findings
HIGH Publisher changed: squid.cloud → wynnch-squid-ai (on 2026-02-25) provenance

This version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.447

2 findings
LOW No provenance attestation provenance

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

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

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

2 findings
LOW No provenance attestation provenance

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-02-19, 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-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.445

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → yossisquid (on 2026-02-12, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (victor-at-squid) on 2026-02-12, 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.444

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → victor-at-squid (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (yossisquid) on 2026-02-11, 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.443

1 finding
LOW No provenance attestation provenance

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

v1.0.442

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mfursov → yossisquid (on 2026-02-06, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (mfursov) on 2026-02-06, 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.441

1 finding
LOW No provenance attestation provenance

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

v1.0.440

2 findings
LOW No provenance attestation provenance

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

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

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → squid.cloud (on 2026-02-05, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (yossisquid) on 2026-02-05, 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.438

1 finding
LOW No provenance attestation provenance

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

v1.0.437

1 finding
LOW No provenance attestation provenance

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

v1.0.436

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: victor-at-squid → yossisquid (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (yossisquid) than the most recent previously approved version (victor-at-squid) on 2026-02-04, 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.435

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (victor-at-squid) than the most recent previously approved version (squid.cloud) on 2026-01-23, 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.434

1 finding
LOW No provenance attestation provenance

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

v1.0.433

2 findings
LOW No provenance attestation provenance

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

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

This version was published by a different npm account (yossisquid) than the most recent previously approved version (squid.cloud) on 2026-01-12, 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.432

1 finding
LOW No provenance attestation provenance

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

v1.0.431

1 finding
LOW No provenance attestation provenance

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

v1.0.430

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yossisquid → squid.cloud (on 2026-01-06, known maintainer) provenance

This version was published by a different npm account (squid.cloud) than the most recent previously approved version (yossisquid) on 2026-01-06, 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.429

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: squid.cloud → yossisquid (on 2026-01-05, known maintainer) provenance

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