@squidcloud/backend
Squid Cloud's backend SDK
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tsoa | AI (phantom-deps): tsoa is used via config/decorators pattern, not direct import; stable for this package. | ai | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.467 | 4 / 3 | |
| 1.0.466 | 4 / 3 | |
| 1.0.465 | 4 / 3 | |
| 1.0.464 | 4 / 3 | |
| 1.0.462 | 4 / 3 | |
| 1.0.458 | 4 / 3 | |
| 1.0.455 | 4 / 3 | |
| 1.0.454 | 4 / 3 | |
| 1.0.453 | 4 / 3 | |
| 1.0.452 | 4 / 3 | |
| 1.0.450 | 4 / 3 | |
| 1.0.414 | 5 / 2 |
v1.0.467
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.465
2 findingsPackage 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 (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 findingsPackage 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 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.462
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.458
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.453
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.450
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.414
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.