@smithy/signature-v4
A standalone implementation of the AWS Signature V4 request signing algorithm
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from smithy-team to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimacy. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript projects. | ai | |
| bogus-package | bogus-package | AI (bogus-package): AWS Smithy core package; low-value signals (no keywords, short README) are false positives for monorepo sub-packages. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 5.6.5 | 3 / 4 | |
| 5.6.4 | 3 / 4 | |
| 5.6.3 | 3 / 4 | |
| 5.6.2 | 3 / 4 | |
| 5.6.1 | 3 / 4 | |
| 5.6.0 | 3 / 4 | |
| 5.5.3 | 3 / 5 | |
| 5.5.2 | 3 / 5 | |
| 5.5.1 | 3 / 5 | |
| 5.5.0 | 3 / 5 | |
| 5.4.7 | 3 / 5 | |
| 5.4.6 | 3 / 5 | |
| 5.4.5 | 3 / 5 | |
| 5.4.4 | 3 / 5 | |
| 5.4.3 | 3 / 5 | |
| 5.4.2 | 3 / 5 | |
| 5.4.1 | 3 / 5 | |
| 5.4.0 | 3 / 5 | |
| 5.3.14 | 8 / 5 | |
| 5.3.13 | 8 / 5 | |
| 5.3.12 | 8 / 5 | |
| 5.3.11 | 8 / 5 | |
| 5.3.10 | 8 / 5 | |
| 5.3.9 | 8 / 5 | |
| 5.3.8 | 8 / 5 | |
| 5.3.7 | 8 / 5 | |
| 5.3.6 | 8 / 5 | |
| 5.3.5 | 8 / 5 | |
| 5.3.4 | 8 / 5 | |
| 5.3.3 | 8 / 5 | |
| 5.3.2 | 8 / 5 | |
| 5.3.1 | 8 / 5 | |
| 5.3.0 | 8 / 5 | |
| 5.2.1 | 8 / 5 | |
| 5.2.0 | 8 / 5 | |
| 5.1.3 | 8 / 5 | |
| 5.1.2 | 8 / 5 | |
| 5.1.1 | 8 / 5 | |
| 5.1.0 | 8 / 5 | |
| 5.0.2 | 8 / 5 | |
| 5.0.1 | 8 / 5 | |
| 5.0.0 | 8 / 5 |
v5.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.6
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.