@aws-crypto/util Apache-2.0 11 versions

@aws-crypto/util

npm Repository Homepage

Helper functions

11

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 gitHead linked

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-ossseebeesagray256lavalerisalkeldraws-crypto-tools-ci-botmattsb42-awsfarleyb-aws

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:uuid	AI (typosquat): @aws-crypto/util is a legitimate AWS Crypto Tools scoped package; the Levenshtein match to 'uuid' is a false positive with no impersonation intent.	ai	2026/04/21
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a standard TypeScript compiler runtime helper; implicit usage via compiler injection is expected and not a risk for TypeScript packages.	ai	2026/04/21

Versions (showing 11 of 11)

Version	Deps	Published
5.2.0	3 / 0	2023-10-16
5.1.0	3 / 0	2023-09-22
5.0.0	3 / 0	2023-07-13
4.0.0	3 / 0	2023-02-20
3.0.0	3 / 0	2023-01-12
2.0.2	3 / 0	2022-09-07
2.0.1	3 / 0	2021-12-09
2.0.0	3 / 0	2021-10-25
1.2.2	3 / 0	2021-10-13
1.2.1	3 / 0	2021-09-17
1.2.0	3 / 0	2021-09-17

v5.1.0

1 finding

LOW No provenance attestation provenance

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

v5.0.0

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.

v4.0.0

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

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

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.