← Home

@dfns/sdk-keyimport-utils-nodejs

npm Repository Homepage
42
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@dfns/dfns-key-import-nodejs AI (dependencies): Sibling package from the same dfns org; consistently used across versions of this package. ai
npm-metadata no-description AI (npm-metadata): Internal SDK utility package; missing description is a style choice, not a malice indicator. ai
phantom-deps phantom-dep:buffer AI (phantom-deps): Monorepo sub-package; buffer is a transitive/polyfill dep declared for bundler compatibility, not directly imported. ai
phantom-deps phantom-dep:cross-fetch AI (phantom-deps): Monorepo sub-package; cross-fetch declared for bundler/env compatibility, stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Tiny utility sub-package in the dfns-sdk-ts monorepo; low metadata signals are expected and not indicative of spam. ai

Versions (showing 42 of 42)

Version Deps Published
0.8.21 3 / 0
0.8.20 3 / 0
0.8.19 3 / 0
0.8.18 3 / 0
0.8.17 3 / 0
0.8.13 3 / 0
0.8.12 3 / 0
0.8.11 3 / 0
0.8.10 3 / 0
0.8.9 3 / 0
0.8.8 3 / 0
0.8.7 3 / 0
0.8.6 3 / 0
0.8.5 3 / 0
0.8.4 3 / 0
0.8.3 3 / 0
0.8.2 3 / 0
0.8.1 3 / 0
0.8.0 3 / 0
0.7.18 1 / 0
0.7.17 1 / 0
0.7.16 1 / 0
0.7.15 3 / 0
0.7.14 1 / 0
0.7.13 1 / 0
0.7.12 1 / 0
0.7.11 3 / 0
0.7.10 3 / 0
0.7.9 3 / 0
0.7.8 3 / 0
0.7.7 3 / 0
0.7.6 3 / 0
0.7.5 3 / 0
0.7.4 3 / 0
0.7.3 3 / 0
0.7.2 3 / 0
0.7.1 3 / 0
0.7.0 3 / 0
0.6.12 4 / 0
0.6.11 4 / 0
0.6.10 4 / 0
0.6.9 4 / 0

v0.8.21

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

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

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

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

1 finding
LOW No provenance attestation provenance

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

v0.8.12

1 finding
LOW No provenance attestation provenance

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

v0.8.11

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: thibault2ss → drunkirishcoder (on 2026-02-12, known maintainer) provenance

This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (thibault2ss) on 2026-02-12, 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.8.10

1 finding
LOW No provenance attestation provenance

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

v0.8.9

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.8.6

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.8.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.8.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.8.1

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.8.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.7.18

1 finding
LOW No provenance attestation provenance

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

v0.7.17

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 → luisalmeida-dfns (on 2025-10-29, known maintainer) provenance

This version was published by a different npm account (luisalmeida-dfns) than the most recent previously approved version (drunkirishcoder) on 2025-10-29, but luisalmeida-dfns 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.7.16

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 → luisalmeida-dfns (on 2025-10-23, known maintainer) provenance

This version was published by a different npm account (luisalmeida-dfns) than the most recent previously approved version (drunkirishcoder) on 2025-10-23, but luisalmeida-dfns 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.7.15

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 → adriendfns (on 2025-10-16, known maintainer) provenance

This version was published by a different npm account (adriendfns) than the most recent previously approved version (drunkirishcoder) on 2025-10-16, but adriendfns 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.7.14

1 finding
LOW No provenance attestation provenance

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

v0.7.13

1 finding
LOW No provenance attestation provenance

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

v0.7.12

1 finding
LOW No provenance attestation provenance

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

v0.7.11

1 finding
LOW No provenance attestation provenance

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

v0.7.10

1 finding
LOW No provenance attestation provenance

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

v0.7.9

1 finding
LOW No provenance attestation provenance

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

v0.7.8

1 finding
LOW No provenance attestation provenance

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

v0.7.7

1 finding
LOW No provenance attestation provenance

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

v0.7.6

1 finding
LOW No provenance attestation provenance

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

v0.7.5

1 finding
LOW No provenance attestation provenance

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

v0.7.4

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.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: drunkirishcoder → thibault2ss (on 2025-06-13, known maintainer) provenance

This version was published by a different npm account (thibault2ss) than the most recent previously approved version (drunkirishcoder) on 2025-06-13, 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.6.12

1 finding
LOW No provenance attestation provenance

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

v0.6.11

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

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

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.