@squidcloud/backend ISC 51 versions

@squidcloud/backend

npm

Squid Cloud's backend SDK

51

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.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tsoa	AI (phantom-deps): tsoa is used via config/decorators pattern, not direct import; stable for this package.	ai	2026/05/02
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Bundled SDK; lodash is a declared dep resolved at build time, not directly imported in source.	ai	2026/04/28
phantom-deps	phantom-dep:graphql	AI (phantom-deps): Bundled SDK; graphql is a declared dep resolved at build time, not directly imported in source.	ai	2026/04/28
phantom-deps	phantom-dep:otrie	AI (phantom-deps): Bundled SDK; otrie is a declared dep resolved at build time, not directly imported in source.	ai	2026/04/28
phantom-deps	phantom-dep:assertic	AI (phantom-deps): Bundled SDK; assertic is a declared dep resolved at build time, not directly imported in source.	ai	2026/04/28

Versions (showing 51 of 332)

View all versions

Version	Deps	Published
1.0.481	4 / 3	2026-07-15
1.0.479	4 / 3	2026-07-13
1.0.478	4 / 3	2026-07-12
1.0.477	4 / 3	2026-07-07
1.0.476	4 / 3	2026-07-01
1.0.475	4 / 3	2026-06-30
1.0.474	4 / 3	2026-06-30
1.0.473	4 / 3	2026-06-17
1.0.472	4 / 3	2026-06-12
1.0.471	4 / 3	2026-06-11
1.0.470	4 / 3	2026-06-10
1.0.469	4 / 3	2026-06-09
1.0.468	4 / 3	2026-06-05
1.0.467	4 / 3	2026-06-03
1.0.466	4 / 3	2026-05-27
1.0.465	4 / 3	2026-05-26
1.0.464	4 / 3	2026-05-18
1.0.462	4 / 3	2026-04-25
1.0.458	4 / 3	2026-04-17
1.0.455	4 / 3	2026-04-03
1.0.454	4 / 3	2026-04-03
1.0.453	4 / 3	2026-04-03
1.0.452	4 / 3	2026-03-30
1.0.450	4 / 3	2026-02-27
1.0.449	5 / 2	2026-02-25
1.0.447	5 / 2	2026-02-23
1.0.446	5 / 2	2026-02-19
1.0.445	5 / 2	2026-02-12
1.0.444	5 / 2	2026-02-11
1.0.443	5 / 2	2026-02-09
1.0.442	5 / 2	2026-02-06
1.0.441	5 / 2	2026-02-06
1.0.440	5 / 2	2026-02-06
1.0.439	5 / 2	2026-02-05
1.0.438	5 / 2	2026-02-04
1.0.437	5 / 2	2026-02-04
1.0.436	5 / 2	2026-02-04
1.0.435	5 / 2	2026-01-23
1.0.434	5 / 2	2026-01-16
1.0.433	5 / 2	2026-01-12
1.0.432	5 / 2	2026-01-08
1.0.431	5 / 2	2026-01-06
1.0.430	5 / 2	2026-01-06
1.0.429	5 / 2	2026-01-05
1.0.428	5 / 2	2025-12-29
1.0.427	5 / 2	2025-12-27
1.0.426	5 / 2	2025-12-26
1.0.425	5 / 2	2025-12-23
1.0.424	5 / 2	2025-12-04
1.0.423	5 / 2	2025-12-03
1.0.422	5 / 2	2025-12-03

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 2026-07-15, 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 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

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

1 finding

LOW No provenance attestation provenance

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

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

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 → squid.cloud (on 2026-02-06, known maintainer) provenance

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

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

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-16, 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-16, 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.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

1 finding

LOW No provenance attestation provenance

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

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.

v1.0.428

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 → squid.cloud (on 2025-12-29, known maintainer) provenance

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

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 → squid.cloud (on 2025-12-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-12-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.426

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 2025-12-26, known maintainer) provenance

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

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 2025-12-23, known maintainer) provenance

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

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 2025-12-04, 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 2025-12-04, 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.423

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 2025-12-03, known maintainer) provenance

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

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 2025-12-03, known maintainer) provenance

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