@contrast/config
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Contrast Security org package; no provenance is consistent across all their releases. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.61.0 | 4 / 0 | |
| 1.60.0 | 4 / 0 | |
| 1.59.0 | 4 / 0 | |
| 1.58.3 | 4 / 0 | |
| 1.55.1 | 4 / 0 | |
| 1.55.0 | 4 / 0 | |
| 1.54.1 | 4 / 0 | |
| 1.54.0 | 4 / 0 | |
| 1.53.0 | 4 / 0 | |
| 1.52.1 | 4 / 0 | |
| 1.52.0 | 4 / 0 | |
| 1.51.0 | 4 / 0 | |
| 1.50.0 | 4 / 0 | |
| 1.49.2 | 3 / 0 | |
| 1.49.1 | 3 / 0 | |
| 1.49.0 | 3 / 0 | |
| 1.48.0 | 3 / 0 | |
| 1.47.0 | 3 / 0 | |
| 1.46.0 | 3 / 0 | |
| 1.45.0 | 3 / 0 | |
| 1.44.0 | 3 / 0 | |
| 1.43.0 | 2 / 0 | |
| 1.42.0 | 2 / 0 | |
| 1.41.0 | 2 / 0 | |
| 1.40.2 | 2 / 0 | |
| 1.40.1 | 2 / 0 | |
| 1.40.0 | 2 / 0 | |
| 1.39.0 | 2 / 0 | |
| 1.38.0 | 2 / 0 | |
| 1.37.0 | 2 / 0 | |
| 1.36.0 | 2 / 0 | |
| 1.35.0 | 2 / 0 | |
| 1.34.0 | 2 / 0 | |
| 1.33.0 | 2 / 0 | |
| 1.32.0 | 2 / 0 | |
| 1.31.0 | 2 / 0 | |
| 1.30.1 | 2 / 0 | |
| 1.30.0 | 2 / 0 | |
| 1.29.0 | 2 / 0 | |
| 1.28.3 | 2 / 0 | |
| 1.28.2 | 2 / 0 | |
| 1.28.1 | 2 / 0 | |
| 1.28.0 | 2 / 0 |
v1.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.