@oneblink/sdk
OneBlink SDK to serve as an entry point for all OneBlink Services in NodeJS
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@oneblink/storage | AI (dependencies): First-party OneBlink sibling package; expected dependency for this SDK. | ai | |
| dependencies | unvetted-dep:@oneblink/sdk-core | AI (dependencies): First-party OneBlink sibling package; expected dependency for this SDK. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 13.1.6 | 8 / 20 | |
| 13.1.5 | 8 / 20 | |
| 13.1.4 | 8 / 20 | |
| 13.1.3 | 8 / 20 | |
| 13.1.2 | 8 / 20 | |
| 13.1.1 | 8 / 20 | |
| 13.1.0 | 8 / 20 | |
| 13.0.0 | 8 / 20 | |
| 12.6.0 | 9 / 24 | |
| 12.5.0 | 9 / 24 | |
| 12.4.0 | 9 / 24 | |
| 12.3.1 | 9 / 24 |
v13.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.