@qvac/infer-base
Base class for inference clients
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@qvac/error | AI (dependencies): Sibling package from same @qvac monorepo (tetherto/qvac); expected internal dependency. | ai | |
| dependencies | unvetted-dep:@qvac/logging | AI (dependencies): Sibling package from same @qvac monorepo (tetherto/qvac); expected internal dependency. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 2 / 3 | |
| 0.5.0 | 2 / 3 | |
| 0.4.1 | 5 / 2 | |
| 0.4.0 | 5 / 2 | |
| 0.3.0 | 5 / 2 | |
| 0.2.2 | 5 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.1 | 5 / 2 | |
| 0.1.0 | 5 / 2 |
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.