← Home

@restatedev/restate-sdk

npm Repository Homepage

Typescript SDK for Restate

49
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

stephanewenrestateslinkydeveloper-restatedevasoli_restatepavel.tcholakovtill_restatenikrestate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js AI (source-diff): Base64-embedded compiled WASM shared core; expected build artifact for this SDK. ai
source-diff obfuscated-file:dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js AI (source-diff): Base64-embedded compiled WASM shared core; expected build artifact for this SDK. ai
provenance publisher-changed AI (provenance): Moved from manual publish to GitHub Actions CI/CD with SLSA attestation. ai
source-diff encoded-string-file:dist/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js AI (source-diff): Base64-encoded WASM binary (\0asm magic); standard for this package's Rust shared core. ai
publish-pattern rapid-publish AI (publish-pattern): CI/CD (GitHub Actions) publishes; rapid successive publishes are normal for automated pipelines. ai
source-diff encoded-string-file:dist/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.cjs AI (source-diff): Base64-encoded WASM binary (AGFzbQ magic); standard pattern for this package's shared-core bindings. ai
maintainer-change maintainer-removed AI (maintainer-change): CI/CD-only publish model; maintainer list change reflects workflow migration, not a takeover. ai
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
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 49 of 49)

Version Deps Published
1.16.1 1 / 1
1.16.0 1 / 1
1.15.1 1 / 1
1.15.0 1 / 1
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.14.0 1 / 1
1.13.0 1 / 1
1.12.0 1 / 1
1.11.1 1 / 1
1.11.0 1 / 1
1.10.4 1 / 1
1.10.3 1 / 1
1.10.2 1 / 1
1.10.1 1 / 1
1.10.0 1 / 1
1.9.1 1 / 1
1.9.0 1 / 1
1.8.4 1 / 1
1.8.3 1 / 1
1.8.2 1 / 1
1.8.1 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
1.5.4 1 / 1
1.5.3 1 / 1
1.5.2 1 / 1
1.5.1 1 / 1
1.5.0 1 / 1
1.4.0 1 / 1
1.3.3 2 / 3
1.3.2 2 / 3
1.3.1 2 / 3
1.3.0 2 / 3
1.2.1 2 / 3
1.2.0 2 / 3
1.1.2 2 / 3
1.1.1 2 / 3
1.1.0 2 / 3
1.0.1 2 / 3
1.0.0 2 / 12

v1.16.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.16.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.11.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.11.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[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.10.4

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[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.5.4

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

3 findings
HIGH New obfuscated file: dist/cjs/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/esm/src/endpoint/handlers/vm/sdk_shared_core_wasm_bindings.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.