← Home

@aws-sdk/xml-builder

XML utilities for the AWS SDK

51
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

amzn-ossaws-sdk-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): aws-sdk-bot publishes hundreds of AWS SDK packages; missing gitHead reflects a CI/CD environment change, not a supply chain risk. Consistent across the SDK package family. ai
provenance no-provenance AI (provenance): AWS SDK packages are published by the well-known aws-sdk-bot; lack of Sigstore attestation is a process gap, not a security threat for this established publisher. ai
dependencies unvetted-dep:fast-xml-parser AI (dependencies): fast-xml-parser is a well-known, widely-used XML parsing library; its use in an AWS SDK XML builder package is entirely appropriate and expected across all versions. ai
bogus-package bogus-package AI (bogus-package): Inflated semver is the standard AWS SDK v3 versioning scheme; short README and no keywords are typical for internal SDK utility packages published by aws-sdk-bot. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard TypeScript runtime helper used as an implicit dependency in compiled AWS SDK packages; stable pattern for this publisher. ai
phantom-deps phantom-dep:@smithy/types AI (phantom-deps): @smithy/types is a framework-scoped type package used by convention across the AWS SDK v3 ecosystem; not a real phantom dependency concern. ai

Versions (showing 51 of 108)

View all versions
Version Deps Published
3.972.26 3 / 6
3.972.25 4 / 5
3.972.24 4 / 5
3.972.23 4 / 5
3.972.22 4 / 5
3.972.21 4 / 5
3.972.20 4 / 5
3.972.19 3 / 5
3.972.18 3 / 5
3.972.17 3 / 5
3.972.16 3 / 5
3.972.15 3 / 5
3.972.14 3 / 5
3.972.13 3 / 5
3.972.12 3 / 5
3.972.11 3 / 5
3.972.10 3 / 5
3.972.9 3 / 5
3.972.8 3 / 5
3.972.7 3 / 5
3.972.6 3 / 5
3.972.5 3 / 5
3.972.4 3 / 5
3.972.3 3 / 5
3.972.2 3 / 5
3.972.1 3 / 5
3.972.0 3 / 5
3.969.0 3 / 5
3.968.0 3 / 5
3.965.0 3 / 5
3.957.0 3 / 5
3.956.0 3 / 5
3.953.0 3 / 5
3.930.0 3 / 5
3.921.0 3 / 5
3.914.0 3 / 5
3.911.0 3 / 5
3.910.0 3 / 5
3.901.0 3 / 5
3.894.0 3 / 5
3.893.0 2 / 5
3.887.0 2 / 5
3.873.0 2 / 5
3.862.0 2 / 5
3.821.0 2 / 5
3.804.0 2 / 5
3.775.0 2 / 5
3.734.0 2 / 5
3.723.0 2 / 5
3.709.0 2 / 5
3.696.0 2 / 5

v3.972.26

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aws-sdk-bot.

v3.972.25

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aws-sdk-bot.

v3.972.24

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aws-sdk-bot.

v3.972.23

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aws-sdk-bot.

v3.972.22

2 findings
INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aws-sdk-bot.

v3.972.21

1 finding
INFO No provenance attestation provenance

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

v3.972.20

1 finding
INFO No provenance attestation provenance

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

v3.972.19

1 finding
INFO No provenance attestation provenance

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