← Home

@aws-lite/client

A simple, fast, extensible AWS client

21
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ryanblockarchitectcibrianlerouxmacdonst

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Implements AWS credential_process spec — executes user-configured credential helper, not arbitrary attacker input. ai
semgrep semgrep:dynamic-require AI (semgrep): Plugin loader pattern; loads user-specified aws-lite plugin modules by name, documented behavior. ai

Versions (showing 21 of 21)

Version Deps Published
0.23.7 1 / 16
0.23.6 1 / 16
0.23.5 1 / 16
0.23.4 1 / 16
0.23.2 1 / 14
0.23.1 1 / 14
0.23.0 1 / 14
0.22.4 1 / 14
0.22.3 1 / 14
0.22.2 1 / 14
0.22.1 1 / 14
0.22.0 1 / 14
0.21.10 1 / 14
0.21.9 2 / 14
0.21.8 2 / 14
0.21.7 2 / 14
0.21.6 2 / 14
0.21.5 2 / 14
0.21.4 2 / 14
0.21.3 2 / 14
0.21.2 2 / 14

v0.23.1

1 finding
LOW No provenance attestation provenance

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

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.4

1 finding
LOW No provenance attestation provenance

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

v0.22.3

1 finding
LOW No provenance attestation provenance

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

v0.22.2

1 finding
LOW No provenance attestation provenance

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

v0.22.1

1 finding
LOW No provenance attestation provenance

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.21.10

1 finding
LOW No provenance attestation provenance

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

v0.21.9

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ryanblock → architectci (on 2024-06-11, known maintainer) provenance

This version was published by a different npm account (architectci) than the most recent previously approved version (ryanblock) on 2024-06-11, but architectci is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.21.8

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ryanblock → architectci (on 2024-06-10, known maintainer) provenance

This version was published by a different npm account (architectci) than the most recent previously approved version (ryanblock) on 2024-06-10, but architectci is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.21.7

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: architectci → ryanblock (on 2024-05-21, known maintainer) provenance

This version was published by a different npm account (ryanblock) than the most recent previously approved version (architectci) on 2024-05-21, but ryanblock is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.21.6

1 finding
LOW No provenance attestation provenance

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

v0.21.5

1 finding
LOW No provenance attestation provenance

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

v0.21.4

1 finding
LOW No provenance attestation provenance

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

v0.21.3

1 finding
LOW No provenance attestation provenance

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

v0.21.2

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.