@contrast/agent SEE LICENSE IN LICENSE 32 versions

@contrast/agent

npm

Assess and Protect agents for Node.js

32

Versions

SEE LICENSE IN LICENSE

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-griffcontrast_adminjcolekaplanmhenry-contrast

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Active package with 340 versions; dormancy signal is a false positive for this well-established Contrast Security agent.	ai	2026/05/08
dependencies	unvetted-dep:@contrast/architecture-components	AI (dependencies): Same @contrast org scope as all other accepted internal deps; consistent monorepo pattern for this package.	ai	2026/05/04
dependencies	unvetted-dep:@contrast/assess	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/common	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/protect	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/sec-obs	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/agentify	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/cli	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/route-coverage	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/library-analysis	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
phantom-deps	phantom-dep:@contrast/cli	AI (phantom-deps): Same-org dep likely used transitively; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/29
phantom-deps	phantom-dep:@contrast/telemetry	AI (phantom-deps): Same-org dep likely used transitively; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/telemetry	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29
dependencies	unvetted-dep:@contrast/core	AI (dependencies): First-party @contrast org dependency; stable pattern across all agent versions.	ai	2026/04/29

Versions (showing 32 of 32)

Version	Deps	Published
5.59.0	10 / 0	2026-06-01
5.58.0	10 / 0	2026-05-18
5.57.0	10 / 0	2026-05-12
5.56.0	10 / 0	2026-05-07
5.55.0	10 / 0	2026-04-24
5.54.1	10 / 0	2026-04-17
5.54.0	10 / 0	2026-04-14
5.53.1	10 / 0	2026-03-31
5.53.0	10 / 0	2026-03-26
5.52.1	9 / 0	2026-03-06
5.52.0	9 / 0	2026-03-03
5.51.0	10 / 0	2026-02-04
5.50.1	10 / 0	2026-01-23
5.50.0	10 / 0	2026-01-15
5.49.0	10 / 0	2025-12-16
5.48.0	10 / 0	2025-12-02
5.47.0	10 / 0	2025-10-29
5.46.0	10 / 0	2025-10-03
5.45.1	10 / 0	2025-09-25
5.45.0	10 / 0	2025-09-25
5.44.0	10 / 0	2025-09-17
5.43.0	10 / 0	2025-08-27
5.42.0	10 / 0	2025-08-08
5.41.0	10 / 0	2025-07-31
5.40.0	10 / 0	2025-07-10
5.39.1	10 / 0	2025-07-01
5.39.0	10 / 0	2025-06-25
5.38.0	10 / 0	2025-06-17
5.37.0	10 / 0	2025-06-16
5.36.0	10 / 0	2025-05-22
5.35.1	10 / 0	2025-05-12
5.35.0	10 / 0	2025-05-07

v5.59.0

1 finding

LOW No provenance attestation provenance

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

v5.58.0

1 finding

LOW No provenance attestation provenance

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

v5.57.0

1 finding

LOW No provenance attestation provenance

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

v5.56.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

v5.52.1

1 finding

LOW No provenance attestation provenance

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

v5.52.0

1 finding

LOW No provenance attestation provenance

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

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

v5.50.1

1 finding

LOW No provenance attestation provenance

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

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

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

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

v5.47.0

1 finding

LOW No provenance attestation provenance

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

v5.46.0

1 finding

LOW No provenance attestation provenance

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

v5.45.1

1 finding

LOW No provenance attestation provenance

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

v5.45.0

1 finding

LOW No provenance attestation provenance

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

v5.44.0

1 finding

LOW No provenance attestation provenance

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

v5.43.0

1 finding

LOW No provenance attestation provenance

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

v5.42.0

1 finding

LOW No provenance attestation provenance

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

v5.41.0

1 finding

LOW No provenance attestation provenance

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

v5.40.0

1 finding

LOW No provenance attestation provenance

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

v5.39.1

1 finding

LOW No provenance attestation provenance

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

v5.39.0

1 finding

LOW No provenance attestation provenance

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

v5.38.0

1 finding

LOW No provenance attestation provenance

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

v5.37.0

1 finding

LOW No provenance attestation provenance

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

v5.36.0

1 finding

LOW No provenance attestation provenance

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

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

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