@contrast/assess No license 29 versions

@contrast/assess

npm

29

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
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get used in URL proxy for taint tracking — expected pattern in a security instrumentation agent.	ai	2026/05/04
phantom-deps	phantom-dep:@contrast/sources	AI (phantom-deps): Same-org sibling dep; may be used indirectly via dynamic loading in instrumentation agent.	ai	2026/05/04
phantom-deps	phantom-dep:@contrast/route-coverage	AI (phantom-deps): Same-org sibling dep; indirect usage pattern expected in this agent.	ai	2026/05/04
phantom-deps	phantom-dep:@contrast/instrumentation	AI (phantom-deps): Same-org sibling dep; indirect usage pattern expected in this agent.	ai	2026/05/04
phantom-deps	phantom-dep:@contrast/stack-trace-factory	AI (phantom-deps): Same-org sibling dep; indirect usage pattern expected in this agent.	ai	2026/05/04

Versions (showing 29 of 29)

Version	Deps	Published
1.75.0	14 / 0	2026-06-01
1.74.0	14 / 0	2026-05-18
1.73.0	14 / 0	2026-05-12
1.72.0	14 / 0	2026-05-07
1.71.1	14 / 0	2026-04-17
1.70.1	14 / 0	2026-03-31
1.70.0	14 / 0	2026-03-26
1.69.1	14 / 0	2026-03-06
1.69.0	14 / 0	2026-03-03
1.68.0	14 / 0	2026-02-04
1.67.2	13 / 0	2026-01-23
1.67.1	13 / 0	2026-01-15
1.67.0	13 / 0	2025-12-16
1.66.0	13 / 0	2025-12-02
1.65.0	13 / 0	2025-10-29
1.64.0	13 / 0	2025-10-03
1.63.0	13 / 0	2025-09-25
1.62.0	13 / 0	2025-09-17
1.61.0	13 / 0	2025-08-27
1.60.0	13 / 0	2025-08-08
1.59.0	13 / 0	2025-07-31
1.58.2	12 / 0	2025-07-10
1.58.1	12 / 0	2025-07-01
1.58.0	12 / 0	2025-06-25
1.57.0	12 / 0	2025-06-17
1.56.0	12 / 0	2025-06-16
1.55.0	12 / 0	2025-05-22
1.54.1	12 / 0	2025-05-12
1.54.0	12 / 0	2025-05-07

v1.75.0

1 finding

LOW No provenance attestation provenance

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

v1.74.0

1 finding

LOW No provenance attestation provenance

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

v1.73.0

1 finding

LOW No provenance attestation provenance

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

v1.72.0

1 finding

LOW No provenance attestation provenance

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

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

v1.70.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: contrast_admin → jcolekaplan (on 2026-03-31, known maintainer) provenance

This version was published by a different npm account (jcolekaplan) than the most recent previously approved version (contrast_admin) on 2026-03-31, but jcolekaplan 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.

v1.70.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: contrast_admin → jcolekaplan (on 2026-03-26, known maintainer) provenance

This version was published by a different npm account (jcolekaplan) than the most recent previously approved version (contrast_admin) on 2026-03-26, but jcolekaplan 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.

v1.69.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: contrast_admin → jcolekaplan (on 2026-03-06, known maintainer) provenance

This version was published by a different npm account (jcolekaplan) than the most recent previously approved version (contrast_admin) on 2026-03-06, but jcolekaplan 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.

v1.69.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: contrast_admin → jcolekaplan (on 2026-03-03, known maintainer) provenance

This version was published by a different npm account (jcolekaplan) than the most recent previously approved version (contrast_admin) on 2026-03-03, but jcolekaplan 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.

v1.68.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: contrast_admin → jcolekaplan (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (jcolekaplan) than the most recent previously approved version (contrast_admin) on 2026-02-04, but jcolekaplan 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.

v1.67.2

1 finding

LOW No provenance attestation provenance

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

v1.67.1

1 finding

LOW No provenance attestation provenance

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

v1.67.0

1 finding

LOW No provenance attestation provenance

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

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

v1.65.0

1 finding

LOW No provenance attestation provenance

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

v1.64.0

1 finding

LOW No provenance attestation provenance

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

v1.63.0

1 finding

LOW No provenance attestation provenance

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

v1.62.0

1 finding

LOW No provenance attestation provenance

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

v1.61.0

1 finding

LOW No provenance attestation provenance

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

v1.60.0

1 finding

LOW No provenance attestation provenance

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

v1.59.0

1 finding

LOW No provenance attestation provenance

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

v1.58.2

1 finding

LOW No provenance attestation provenance

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

v1.58.1

1 finding

LOW No provenance attestation provenance

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

v1.58.0

1 finding

LOW No provenance attestation provenance

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

v1.57.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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