← Home

@cardano-ogmios/client

npm Repository Homepage
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ktorz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Known CardanoSolutions org maintainer rotation; publisher has long track record in the ecosystem. ai
publish-pattern dormant-publish AI (publish-pattern): Major version bump (6.x→7.0.0) explains dormancy; consistent with upstream Ogmios protocol versioning cadence. ai
npm-metadata url-dep:json-schema-to-typescript AI (npm-metadata): Git URL points to CardanoSolutions fork of the same org; devDependency only, not shipped to consumers. ai
phantom-deps phantom-dep:ws AI (phantom-deps): ws is a legitimate runtime dependency used via isomorphic-ws; phantom-dep is a false positive for this package. ai
phantom-deps phantom-dep:@types/json-bigint AI (phantom-deps): Type package declared as runtime dep for json-bigint types; false positive for this package. ai

Versions (showing 17 of 17)

Version Deps Published
7.0.0 10 / 23
6.14.0 10 / 23
6.13.0 10 / 23
6.12.0 10 / 23
6.11.2 10 / 23
6.11.1 10 / 23
6.11.0 10 / 23
6.10.0 10 / 23
6.9.0 10 / 23
6.8.0 10 / 23
6.7.0 10 / 23
6.6.2 10 / 23
6.6.1 10 / 23
6.6.0 10 / 23
6.5.0 10 / 23
6.4.0 10 / 23
6.3.0 10 / 23

v7.0.0

1 finding
LOW No provenance attestation provenance

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

v6.11.2

1 finding
LOW No provenance attestation provenance

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

v6.11.1

1 finding
LOW No provenance attestation provenance

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

v6.11.0

1 finding
LOW No provenance attestation provenance

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

v6.10.0

1 finding
LOW No provenance attestation provenance

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

v6.8.0

1 finding
LOW No provenance attestation provenance

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

v6.7.0

1 finding
LOW No provenance attestation provenance

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

v6.6.2

1 finding
LOW No provenance attestation provenance

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

v6.6.1

1 finding
LOW No provenance attestation provenance

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

v6.6.0

1 finding
LOW No provenance attestation provenance

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

v6.5.0

1 finding
LOW No provenance attestation provenance

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

v6.4.0

1 finding
LOW No provenance attestation provenance

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

v6.3.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.