@cuboapp/api-backend
Backend Api for CuboApp
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:pg | AI (phantom-deps): pg is a runtime dep used via config/indirect references in this backend package; stable false positive. | ai | |
| phantom-deps | phantom-dep:yjs | AI (phantom-deps): yjs referenced in config files consistent with CRDT usage in this backend; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.38 | 9 / 2 | |
| 1.0.37 | 9 / 2 | |
| 1.0.35 | 9 / 2 | |
| 1.0.34 | 9 / 2 | |
| 1.0.11 | 4 / 2 |
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.