@develit-io/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, 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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Added 'cloudflare' is the official Cloudflare SDK, consistent with this package's Workers-oriented purpose. | ai | |
| dependencies | unvetted-dep:cloudflare | AI (dependencies): cloudflare is Cloudflare's official SDK; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established internal SDK with 180 versions; lack of provenance is consistent across all releases. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 12.5.0 | 4 / 2 | |
| 12.4.1 | 4 / 2 | |
| 12.4.0 | 4 / 2 | |
| 12.3.1 | 4 / 2 | |
| 12.3.0 | 4 / 2 | |
| 12.2.1 | 4 / 2 | |
| 12.2.0 | 4 / 2 | |
| 12.1.0 | 4 / 2 | |
| 12.0.0 | 4 / 2 | |
| 11.3.0 | 4 / 2 | |
| 11.2.0 | 4 / 2 | |
| 11.1.0 | 4 / 2 | |
| 11.0.5 | 4 / 2 | |
| 11.0.4 | 4 / 2 | |
| 11.0.3 | 4 / 2 | |
| 11.0.2 | 4 / 1 | |
| 11.0.1 | 4 / 1 | |
| 11.0.0 | 4 / 1 | |
| 10.0.5 | 4 / 1 | |
| 10.0.4 | 4 / 1 | |
| 10.0.3 | 4 / 1 | |
| 10.0.2 | 3 / 1 | |
| 10.0.1 | 3 / 1 | |
| 10.0.0 | 3 / 1 | |
| 9.11.16 | 3 / 1 | |
| 9.11.15 | 3 / 1 | |
| 9.11.14 | 3 / 1 | |
| 9.11.13 | 3 / 1 | |
| 9.11.12 | 3 / 1 | |
| 9.11.11 | 3 / 1 | |
| 9.11.10 | 3 / 1 | |
| 9.11.9 | 3 / 1 | |
| 9.11.8 | 3 / 1 | |
| 9.11.7 | 3 / 1 | |
| 9.11.6 | 3 / 1 | |
| 9.11.5 | 3 / 1 | |
| 9.11.4 | 3 / 1 | |
| 9.11.3 | 3 / 1 | |
| 9.11.2 | 3 / 1 | |
| 9.11.1 | 3 / 1 | |
| 9.11.0 | 3 / 1 | |
| 9.10.4 | 3 / 1 | |
| 9.10.3 | 3 / 1 | |
| 9.10.1 | 3 / 1 | |
| 9.10.0 | 3 / 1 | |
| 9.9.1 | 3 / 1 | |
| 9.9.0 | 3 / 1 | |
| 9.8.2 | 3 / 1 | |
| 9.8.1 | 3 / 2 | |
| 9.8.0 | 3 / 2 | |
| 9.7.1 | 3 / 2 | |
| 9.7.0 | 5 / 2 | |
| 9.6.2 | 5 / 2 | |
| 9.6.1 | 5 / 2 | |
| 9.6.0 | 5 / 2 | |
| 9.5.2 | 5 / 2 | |
| 9.5.1 | 5 / 2 | |
| 9.5.0 | 5 / 2 | |
| 9.4.3 | 5 / 2 | |
| 9.4.2 | 5 / 2 | |
| 9.4.1 | 5 / 2 | |
| 9.4.0 | 5 / 2 | |
| 9.3.0 | 5 / 2 | |
| 9.2.0 | 5 / 2 | |
| 9.1.6 | 5 / 2 | |
| 9.1.5 | 5 / 2 | |
| 9.1.4 | 5 / 2 | |
| 9.1.3 | 5 / 2 | |
| 9.1.2 | 5 / 2 | |
| 9.1.1 | 5 / 2 | |
| 9.1.0 | 5 / 2 | |
| 9.0.3 | 5 / 2 | |
| 9.0.2 | 5 / 2 | |
| 9.0.1 | 5 / 2 | |
| 9.0.0 | 5 / 2 | |
| 8.6.3 | 6 / 1 | |
| 8.6.2 | 6 / 1 | |
| 8.6.1 | 6 / 1 | |
| 8.6.0 | 6 / 1 | |
| 8.5.1 | 6 / 1 | |
| 8.5.0 | 6 / 1 | |
| 8.4.1 | 6 / 1 | |
| 8.4.0 | 6 / 1 | |
| 8.3.1 | 6 / 1 | |
| 8.3.0 | 6 / 1 | |
| 8.2.1 | 6 / 1 | |
| 8.2.0 | 6 / 1 | |
| 8.1.0 | 6 / 1 | |
| 8.0.0 | 6 / 1 | |
| 7.0.2 | 6 / 1 | |
| 7.0.1 | 6 / 1 | |
| 7.0.0 | 6 / 1 | |
| 6.0.0 | 6 / 1 | |
| 5.47.0 | 7 / 1 | |
| 5.46.0 | 7 / 1 | |
| 5.45.0 | 7 / 1 | |
| 5.44.0 | 7 / 1 | |
| 5.43.0 | 7 / 1 | |
| 5.42.0 | 7 / 1 | |
| 5.41.0 | 7 / 1 |
v12.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
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 (kleinpetr) than the most recent previously approved version (ffdevelit) on 2025-12-22, but kleinpetr 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.
v9.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.