@smithy/eventstream-serde-config-resolver
[](https://www.npmjs.com/package/@smithy/eventstream-serde-config-resolver) [: Transition to GitHub Actions CI/CD publishing; consistent with SLSA provenance attestation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable omission across versions of this AWS Smithy internal package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency used via TypeScript importHelpers. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.5.1 | 2 / 1 | |
| 4.5.0 | 2 / 1 | |
| 4.4.7 | 2 / 1 | |
| 4.4.6 | 2 / 1 | |
| 4.4.5 | 2 / 1 | |
| 4.4.4 | 2 / 1 | |
| 4.4.3 | 2 / 1 | |
| 4.4.2 | 2 / 1 | |
| 4.4.1 | 2 / 1 | |
| 4.4.0 | 2 / 1 | |
| 4.3.14 | 2 / 4 | |
| 4.3.13 | 2 / 4 | |
| 4.3.12 | 2 / 4 | |
| 4.3.11 | 2 / 4 | |
| 4.3.10 | 2 / 4 | |
| 4.3.9 | 2 / 4 | |
| 4.3.8 | 2 / 4 | |
| 4.3.7 | 2 / 4 | |
| 4.3.6 | 2 / 4 | |
| 4.3.5 | 2 / 4 | |
| 4.3.4 | 2 / 4 | |
| 4.3.3 | 2 / 4 | |
| 4.3.2 | 2 / 4 | |
| 4.3.1 | 2 / 4 | |
| 4.3.0 | 2 / 4 | |
| 4.2.1 | 2 / 4 | |
| 4.2.0 | 2 / 4 | |
| 4.1.3 | 2 / 4 | |
| 4.1.2 | 2 / 4 | |
| 4.1.1 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.1 | 2 / 4 | |
| 4.0.0 | 2 / 4 |
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.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.
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.