@restatedev/restate-sdk
Typescript SDK for Restate
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA Sigstore attestation present; gitHead absence is a cosmetic metadata gap, not a supply-chain risk for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): CI/CD-only publish model; maintainer list change reflects workflow migration, not a takeover. | ai | |
| source-diff | encoded-string-file:dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js | AI (source-diff): Base64-encoded WebAssembly binary via wasm-bindgen; standard pattern for this SDK's WASM core. | ai | |
| source-diff | encoded-string-file:dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js | AI (source-diff): Same wasm-bindgen WASM binary in ESM build; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.14.5 | 1 / 1 | |
| 1.14.4 | 1 / 1 | |
| 1.14.3 | 1 / 1 | |
| 1.14.2 | 1 / 1 | |
| 1.14.1 | 1 / 1 | |
| 1.10.1 | 1 / 1 | |
| 1.10.0 | 1 / 1 | |
| 1.9.0 | 1 / 1 | |
| 1.8.4 | 1 / 1 | |
| 1.8.0 | 1 / 1 | |
| 1.7.3 | 1 / 1 | |
| 1.7.2 | 1 / 1 | |
| 1.7.1 | 1 / 1 | |
| 1.7.0 | 1 / 1 | |
| 1.6.1 | 1 / 1 | |
| 1.6.0 | 1 / 1 |
v1.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.14.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v1.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.