← Home

@contrast/core

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

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@contrast/fn-inspect AI (phantom-deps): Same-org scoped dep; likely used transitively or conditionally within the Contrast agent ecosystem. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @contrast/core is a long-established Contrast Security agent package, not a typosquat of cors. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads a package.json file path resolved from env/filesystem, not arbitrary user input. ai
phantom-deps phantom-dep:@contrast/logger AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for transitive/re-exported deps within a monorepo. ai
phantom-deps phantom-dep:@contrast/patcher AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for transitive/re-exported deps within a monorepo. ai

Versions (showing 17 of 17)

Version Deps Published
1.63.3 10 / 0
1.63.2 10 / 0
1.60.1 11 / 0
1.60.0 11 / 0
1.59.1 11 / 0
1.59.0 11 / 0
1.58.0 11 / 0
1.57.1 11 / 0
1.57.0 11 / 0
1.56.0 11 / 0
1.55.0 10 / 0
1.54.2 10 / 0
1.54.1 10 / 0
1.54.0 10 / 0
1.53.0 10 / 0
1.52.0 10 / 0
1.51.0 10 / 0

v1.63.3

1 finding
LOW No provenance attestation provenance

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

v1.63.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@contrast/core' is 1 edit(s) away from popular package 'cors'.

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

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@contrast/core' is 1 edit(s) away from popular package 'cors'.

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.55.0

1 finding
LOW No provenance attestation provenance

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

v1.54.2

1 finding
LOW No provenance attestation provenance

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

v1.54.1

1 finding
LOW No provenance attestation provenance

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

v1.54.0

1 finding
LOW No provenance attestation provenance

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

v1.53.0

1 finding
LOW No provenance attestation provenance

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

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