@effect-aws/client-lambda
Effectful AWS Lambda client
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/LambdaService.d.ts | AI (source-diff): Long-line .d.ts type re-exports, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/dts/LambdaService.d.ts | AI (source-diff): Long-line .d.ts type re-exports, not obfuscated code. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with regular version cadence on npm; no behavior change found. | ai | |
| dependencies | unvetted-dep:@effect-aws/commons | AI (dependencies): Sibling package from the same effect-aws monorepo; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.11.3 | 2 / 0 | |
| 1.11.1 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.9 | 2 / 0 | |
| 1.10.7 | 2 / 0 | |
| 1.10.6 | 2 / 0 | |
| 1.10.3 | 2 / 0 | |
| 1.10.2 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.5 | 2 / 0 | |
| 1.9.3 | 2 / 0 | |
| 1.9.0 | 2 / 0 | |
| 1.7.0 | 1 / 14 | |
| 1.6.0 | 1 / 14 | |
| 1.5.1 | 1 / 14 | |
| 1.5.0 | 1 / 14 | |
| 1.4.0 | 2 / 13 | |
| 1.1.1 | 2 / 15 | |
| 1.1.0 | 2 / 19 | |
| 1.0.2 | 2 / 19 | |
| 1.0.1 | 2 / 19 |
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.