@smithy/service-error-classification
[](https://www.npmjs.com/package/@smithy/service-error-classification) [](h
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 to GitHub Actions CI/CD publishing is expected for smithy-lang monorepo. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable omission across versions of this established AWS package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency used via TypeScript importHelpers. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 4.5.15 | 2 / 1 | |
| 4.5.14 | 2 / 1 | |
| 4.5.13 | 2 / 1 | |
| 4.5.12 | 2 / 1 | |
| 4.5.11 | 2 / 1 | |
| 4.5.10 | 2 / 1 | |
| 4.5.9 | 2 / 1 | |
| 4.5.8 | 2 / 1 | |
| 4.5.7 | 2 / 1 | |
| 4.5.6 | 2 / 1 | |
| 4.5.5 | 2 / 1 | |
| 4.5.4 | 2 / 1 | |
| 4.5.3 | 2 / 1 | |
| 4.5.2 | 2 / 1 | |
| 4.5.1 | 2 / 1 | |
| 4.5.0 | 2 / 1 | |
| 4.4.7 | 2 / 1 | |
| 4.4.6 | 2 / 0 | |
| 4.4.5 | 2 / 0 | |
| 4.4.4 | 2 / 0 | |
| 4.4.3 | 2 / 0 | |
| 4.4.2 | 2 / 0 | |
| 4.4.1 | 2 / 0 | |
| 4.4.0 | 2 / 0 | |
| 4.3.1 | 1 / 4 | |
| 4.3.0 | 1 / 4 | |
| 4.2.14 | 1 / 4 | |
| 4.2.13 | 1 / 4 | |
| 4.2.12 | 1 / 4 | |
| 4.2.11 | 1 / 4 | |
| 4.2.10 | 1 / 4 | |
| 4.2.9 | 1 / 4 | |
| 4.2.8 | 1 / 4 | |
| 4.2.7 | 1 / 4 | |
| 4.2.6 | 1 / 4 | |
| 4.2.5 | 1 / 4 | |
| 4.2.4 | 1 / 4 | |
| 4.2.3 | 1 / 4 | |
| 4.2.2 | 1 / 4 | |
| 4.2.1 | 1 / 4 | |
| 4.2.0 | 1 / 4 | |
| 4.1.2 | 1 / 4 | |
| 4.1.1 | 1 / 4 | |
| 4.1.0 | 1 / 4 | |
| 4.0.7 | 1 / 4 | |
| 4.0.6 | 1 / 4 | |
| 4.0.5 | 1 / 4 | |
| 4.0.4 | 1 / 4 | |
| 4.0.3 | 1 / 4 | |
| 4.0.2 | 1 / 4 | |
| 4.0.1 | 1 / 4 | |
| 4.0.0 | 1 / 4 |
v4.5.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.