@aws/durable-execution-sdk-js
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard import.meta detection workaround in CJS bundle; stable pattern for this package. | ai | |
| npm-metadata | url-dep:eslint-plugin-filename-convention | AI (npm-metadata): devDependency only; local eslint plugin not shipped in published artifact. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 1 / 15 | |
| 1.1.5 | 1 / 15 | |
| 1.1.4 | 1 / 15 | |
| 1.1.3 | 1 / 15 | |
| 1.1.2 | 1 / 15 | |
| 1.1.1 | 1 / 15 | |
| 1.1.0 | 1 / 15 | |
| 1.0.3 | 1 / 15 | |
| 1.0.2 | 1 / 15 | |
| 1.0.1 | 1 / 16 | |
| 1.0.0 | 1 / 15 |
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.