← Home

@smithy/signature-v4a

45
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

smithy-teamaws-sdk-bot

Versions (showing 45 of 45)

Version Deps Published
3.5.6 4 / 4
3.5.5 4 / 4
3.5.4 4 / 4
3.5.3 4 / 4
3.5.2 4 / 4
3.5.1 4 / 4
3.5.0 4 / 4
3.4.3 4 / 4
3.4.2 4 / 4
3.4.1 4 / 4
3.4.0 4 / 4
3.3.3 4 / 5
3.3.2 4 / 5
3.3.1 4 / 5
3.3.0 4 / 5
3.2.8 4 / 5
3.2.7 4 / 5
3.2.5 4 / 5
3.2.4 4 / 5
3.2.3 4 / 5
3.2.2 4 / 5
3.2.1 4 / 5
3.2.0 4 / 5
3.1.14 5 / 6
3.1.13 5 / 6
3.1.12 5 / 6
3.1.11 5 / 6
3.1.10 5 / 6
3.1.9 5 / 6
3.1.8 5 / 6
3.1.7 5 / 6
3.1.6 5 / 6
3.1.5 5 / 6
3.1.4 5 / 6
3.1.3 5 / 6
3.1.2 5 / 6
3.1.1 5 / 6
3.1.0 5 / 6
3.0.7 5 / 6
3.0.6 5 / 6
3.0.5 5 / 6
3.0.4 5 / 6
3.0.3 5 / 6
3.0.2 5 / 6
3.0.1 5 / 6

v3.5.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.3.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.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.

v3.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.