← Home

@cordisjs/plugin-http

10
Versions
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

shigma

Keywords

httpfetchaxioshttpsundiciclientrequestcordisplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:cosmokit AI (dependencies): cosmokit is a core utility library in the Cordis/cordiverse ecosystem by the same maintainer (Shigma); expected dependency for all Cordis plugins. ai
dependencies unvetted-dep:schemastery AI (dependencies): schemastery is a schema validation library in the Cordis/cordiverse ecosystem by the same maintainer; expected dependency for Cordis plugins. ai
dependencies unvetted-dep:@cordisjs/fetch-file AI (dependencies): @cordisjs/fetch-file is a first-party cordiverse package by the same maintainer; expected companion dependency for this HTTP plugin. ai

Versions (showing 10 of 10)

Version Deps Published
1.5.1 3 / 3
1.5.0 3 / 3
1.4.0 3 / 3
1.3.0 3 / 3
1.2.0 2 / 3
1.1.0 2 / 2
1.0.3 2 / 2
1.0.2 2 / 2
1.0.1 2 / 2
1.0.0 2 / 2

v1.5.1

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.

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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