← Home

@effect-aws/client-cloudwatch

npm Repository Homepage

Effectful AWS CloudWatch client

15
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

f1oyd

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): First-party sibling package from same author/monorepo, not an unvetted third-party dep. ai
source-diff large-new-source-files AI (source-diff): Generated dist files for AWS SDK wrapper, consistent with package purpose. ai
dependencies unvetted-dep:@aws-sdk/client-cloudwatch AI (dependencies): Official AWS SDK v3 client; well-known, widely trusted package. ai
dependencies unvetted-dep:@effect-aws/commons AI (dependencies): Internal monorepo shared library from the same effect-aws project; stable false positive. ai

Versions (showing 15 of 15)

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.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.2.0 1 / 14
1.1.0 1 / 14
1.0.1 1 / 14
1.0.0 1 / 14

v1.11.3

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.6

1 finding
LOW No provenance attestation provenance

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

v1.10.3

1 finding
LOW No provenance attestation provenance

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

v1.10.2

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.5

1 finding
LOW No provenance attestation provenance

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

v1.9.3

1 finding
LOW No provenance attestation provenance

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

v1.9.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.