@dfns/sdk-awskmssigner No license 60 versions

@dfns/sdk-awskmssigner

npm Repository Homepage

60

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): buffer/cross-fetch are common, well-known utility deps, not credential/exfil vectors.	ai	2026/07/11
maintainer-change	maintainer-added	AI (maintainer-change): Known maintainer rotation within Dfns org, no behavioral change.	ai	2026/07/11
bogus-package	bogus-package	AI (bogus-package): Small scoped SDK helper package, legitimate despite sparse metadata.	ai	2026/07/11
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Used indirectly per package structure; stable false positive.	ai	2026/07/11
maintainer-change	maintainer-removed	AI (maintainer-change): Normal maintainer rotation, not a takeover pattern.	ai	2026/07/11
phantom-deps	phantom-dep:cross-fetch	AI (phantom-deps): Polyfill dependency; stable pattern for this package.	ai	2026/04/29
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Polyfill dependency; stable pattern for this package.	ai	2026/04/29

Versions (showing 60 of 60)

Version	Deps	Published
0.8.25	3 / 0	2026-07-09
0.8.24	3 / 0	2026-07-06
0.8.23	3 / 0	2026-07-01
0.8.21	3 / 0	2026-05-21
0.8.20	3 / 0	2026-05-01
0.8.19	3 / 0	2026-04-27
0.8.18	3 / 0	2026-04-24
0.8.17	3 / 0	2026-04-15
0.8.13	3 / 0	2026-03-26
0.8.12	3 / 0	2026-02-26
0.8.11	3 / 0	2026-02-12
0.8.10	3 / 0	2026-02-05
0.8.9	3 / 0	2026-01-30
0.8.8	3 / 0	2026-01-19
0.8.7	3 / 0	2026-01-14
0.8.6	3 / 0	2026-01-07
0.8.5	3 / 0	2025-12-22
0.8.4	3 / 0	2025-12-11
0.8.3	3 / 0	2025-11-26
0.8.2	3 / 0	2025-11-19
0.8.1	3 / 0	2025-11-14
0.8.0	3 / 0	2025-11-06
0.7.18	1 / 0	2025-10-31
0.7.2	3 / 0	2025-06-26
0.7.1	3 / 0	2025-06-20
0.7.0	1 / 0	2025-06-13
0.6.12	4 / 0	2025-06-05
0.6.11	4 / 0	2025-05-23
0.6.10	4 / 0	2025-05-08
0.6.8	4 / 0	2025-04-09
0.6.7	4 / 0	2025-04-04
0.6.6	4 / 0	2025-03-28
0.6.5	4 / 0	2025-03-21
0.6.4	4 / 0	2025-03-06
0.6.3	4 / 0	2025-02-20
0.6.2	4 / 0	2025-01-30
0.6.1	4 / 0	2024-12-20
0.6.0	4 / 0	2024-12-11
0.5.9	4 / 0	2024-11-01
0.5.8	4 / 0	2024-10-24
0.5.7	4 / 0	2024-10-08
0.5.6	4 / 0	2024-09-13
0.5.5	1 / 0	2024-08-08
0.5.4	1 / 0	2024-07-26
0.5.3	1 / 0	2024-07-22
0.5.2	4 / 0	2024-06-27
0.5.0	4 / 0	2024-06-10
0.4.3	4 / 0	2024-05-08
0.4.2	1 / 0	2024-04-18
0.4.1	4 / 0	2024-04-03
0.4.0	4 / 0	2024-03-28
0.3.4	4 / 0	2024-03-21
0.3.3	4 / 0	2024-03-12
0.3.2	4 / 0	2024-02-21
0.3.1	4 / 0	2024-02-08
0.3.0	4 / 0	2024-02-01
0.2.5	4 / 0	2024-01-24
0.2.4	4 / 0	2024-01-19
0.2.3	4 / 0	2024-01-16
0.2.2	4 / 0	2024-01-04

v0.8.25

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.24

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.23

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: drunkirishcoder → thibault2ss (on 2026-01-19, known maintainer) provenance

This version was published by a different npm account (thibault2ss) than the most recent previously approved version (drunkirishcoder) on 2026-01-19, but thibault2ss is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: drunkirishcoder → ncornwell (on 2025-12-22, known maintainer) provenance

This version was published by a different npm account (ncornwell) than the most recent previously approved version (drunkirishcoder) on 2025-12-22, but ncornwell is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: drunkirishcoder → ncornwell (on 2025-11-14, known maintainer) provenance

This version was published by a different npm account (ncornwell) than the most recent previously approved version (drunkirishcoder) on 2025-11-14, but ncornwell is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-04-09, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-04-09, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.7

1 finding

LOW No provenance attestation provenance

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

v0.6.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-03-28, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-03-28, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-03-21, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-03-21, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-03-06, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-03-06, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-02-20, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2025-01-30, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2025-01-30, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2024-12-20, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2024-12-20, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → thibault2ss (on 2024-12-11, known maintainer) provenance

This version was published by a different npm account (thibault2ss) than the most recent previously approved version (ncornwell) on 2024-12-11, but thibault2ss is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.9

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2024-11-01, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2024-11-01, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ncornwell → drunkirishcoder (on 2024-10-24, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (ncornwell) on 2024-10-24, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

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.

v0.5.3

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.

v0.5.2

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.

v0.5.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.

v0.4.3

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.

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: drunkirishcoder → ncornwell (on 2024-01-16, known maintainer) provenance

This version was published by a different npm account (ncornwell) than the most recent previously approved version (drunkirishcoder) on 2024-01-16, but ncornwell is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.2

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.