@effect-aws/client-cloudwatch-logs
Effectful AWS CloudWatch Logs 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/CloudWatchLogsService.d.ts | AI (source-diff): Auto-generated TypeScript .d.ts with long type-union lines, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/dts/CloudWatchLogsService.d.ts | AI (source-diff): Auto-generated TypeScript .d.ts with long type-union lines, not obfuscated code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @effect-aws/commons is a first-party sibling package by the same author/monorepo. | ai | |
| dependencies | unvetted-dep:@effect-aws/commons | AI (dependencies): Sibling package in the same effect-aws monorepo; not an independent supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; low-risk AWS wrapper with no other signals. | ai |
Versions (showing 18 of 18)
| 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.8 | 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.3.0 | 1 / 14 | |
| 1.2.0 | 1 / 14 | |
| 1.1.0 | 1 / 14 | |
| 1.0.1 | 1 / 14 | |
| 1.0.0 | 1 / 14 |
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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
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.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.