@contrast/esm-hooks No license 25 versions

@contrast/esm-hooks

npm

25

Versions

—

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

tough-griffchrisdunnecontrast_adminjcolekaplancontrastsecmhenry-contrastnbuckwalt

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): jcolekaplan is an established Contrast Security publisher with 13 approved packages; transition appears legitimate.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Enterprise security vendor package; sparse public metadata is expected for internal tooling components.	ai	2026/05/04

Versions (showing 25 of 25)

Version	Deps	Published
2.38.5	6 / 0	2026-06-01
2.38.4	6 / 0	2026-05-07
2.38.3	6 / 0	2026-04-24
2.38.2	6 / 0	2026-04-17
2.38.1	6 / 0	2026-03-31
2.38.0	6 / 0	2026-03-26
2.37.1	6 / 0	2026-03-06
2.37.0	6 / 0	2026-03-03
2.36.0	6 / 0	2026-02-04
2.35.2	6 / 0	2026-01-23
2.35.1	6 / 0	2026-01-15
2.35.0	6 / 0	2025-12-16
2.34.1	6 / 0	2025-12-02
2.34.0	6 / 0	2025-10-29
2.33.0	6 / 0	2025-10-03
2.32.0	6 / 0	2025-09-25
2.31.0	6 / 0	2025-09-17
2.30.0	6 / 0	2025-08-27
2.29.0	6 / 0	2025-07-31
2.28.2	6 / 0	2025-07-10
2.28.1	6 / 0	2025-07-01
2.28.0	6 / 0	2025-06-17
2.27.0	6 / 0	2025-06-16
2.26.0	6 / 0	2025-05-22
2.25.0	6 / 0	2025-05-07

v2.38.5

1 finding

LOW No provenance attestation provenance

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

v2.38.4

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-05-07) provenance

This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.38.3

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-04-24) provenance

This version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.38.2

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-04-17) provenance

This version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.38.1

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-03-31) provenance

This version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.38.0

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.37.1

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-03-06) provenance

This version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.37.0

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-03-03) provenance

This version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.36.0

2 findings

HIGH Publisher changed: contrast_admin → jcolekaplan (on 2026-02-04) provenance

This version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.35.2

1 finding

LOW No provenance attestation provenance

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

v2.35.1

1 finding

LOW No provenance attestation provenance

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

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

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

v2.34.0

1 finding

LOW No provenance attestation provenance

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

v2.33.0

1 finding

LOW No provenance attestation provenance

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

v2.32.0

1 finding

LOW No provenance attestation provenance

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

v2.31.0

1 finding

LOW No provenance attestation provenance

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

v2.30.0

1 finding

LOW No provenance attestation provenance

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

v2.29.0

1 finding

LOW No provenance attestation provenance

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

v2.28.2

1 finding

LOW No provenance attestation provenance

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

v2.28.1

1 finding

LOW No provenance attestation provenance

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

v2.28.0

1 finding

LOW No provenance attestation provenance

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

v2.27.0

1 finding

LOW No provenance attestation provenance

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

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

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