← Home

@redhat-cloud-services/vulnerabilities-client

npm Repository Homepage

If you want to use [RedHatInsights/vulnerability-engine](https://github.com/RedHatInsights/vulnerability-engine) you shouldn't use get requests directly, but rather use this client to integrate with this service.

11
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

karelhalahyperkidflorkbrchmulder

Versions (showing 11 of 11)

Version Deps Published
2.1.13 2 / 1
2.1.12 2 / 1
2.1.7 2 / 1
2.1.6 2 / 1
2.1.5 2 / 1
2.1.4 2 / 2
2.1.3 2 / 2
2.1.2 2 / 2
2.1.1 2 / 2
2.1.0 2 / 2
2.0.0 2 / 2

v2.1.13

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.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.0.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.