@lemmaoracle/sdk
[](https://www.npmjs.com/package/@lemmaoracle/sdk) [](https://www.typescriptlang.org/)
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): buffer is a well-known Node.js polyfill; addition is consistent with browser-compatibility needs of a crypto SDK. | ai | |
| phantom-deps | phantom-dep:onnxruntime-node | AI (phantom-deps): onnxruntime-node is a peer/config-level dep for ONNX inference; not directly imported in user code is expected. | ai | |
| dependencies | unvetted-dep:@docknetwork/crypto-wasm | AI (dependencies): Legitimate WASM crypto library from Dock.io; consistent with this SDK's ZK/credential use case. | ai | |
| provenance | no-provenance | AI (provenance): New SDK package; lack of provenance is common and not a security signal here. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.0.40 | 9 / 8 | |
| 0.0.39 | 9 / 8 | |
| 0.0.38 | 9 / 8 | |
| 0.0.37 | 9 / 8 | |
| 0.0.36 | 9 / 8 | |
| 0.0.35 | 9 / 8 | |
| 0.0.34 | 9 / 8 | |
| 0.0.33 | 9 / 8 | |
| 0.0.32 | 9 / 8 | |
| 0.0.31 | 9 / 8 | |
| 0.0.30 | 9 / 8 | |
| 0.0.29 | 9 / 8 | |
| 0.0.27 | 9 / 8 | |
| 0.0.26 | 9 / 8 | |
| 0.0.24 | 8 / 8 | |
| 0.0.23 | 8 / 8 | |
| 0.0.22 | 8 / 8 | |
| 0.0.21 | 8 / 8 | |
| 0.0.17 | 8 / 8 | |
| 0.0.15 | 8 / 8 | |
| 0.0.14 | 8 / 8 | |
| 0.0.13 | 8 / 8 | |
| 0.0.12 | 8 / 8 | |
| 0.0.11 | 10 / 8 | |
| 0.0.10 | 10 / 8 | |
| 0.0.9 | 10 / 8 | |
| 0.0.8 | 10 / 8 | |
| 0.0.7 | 10 / 8 | |
| 0.0.6 | 10 / 8 | |
| 0.0.5 | 9 / 8 | |
| 0.0.4 | 9 / 8 | |
| 0.0.3 | 9 / 8 | |
| 0.0.2 | 9 / 8 | |
| 0.0.1 | 9 / 8 |
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.