← Home

@types/co-body

npm Repository Homepage

TypeScript definitions for co-body

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@types/qs AI (dependencies): @types/qs is a DefinitelyTyped type definition package; its use as a dependency in another @types package is expected and benign. ai
provenance no-provenance AI (provenance): DefinitelyTyped packages published via the `types` publisher consistently lack Sigstore provenance; this is a known ecosystem-wide pattern, not a risk indicator. ai
phantom-deps phantom-dep:@types/qs AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not direct imports. This is expected behavior for DefinitelyTyped packages. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a standard TypeScript ambient type package loaded by convention, not direct import. Expected for DefinitelyTyped packages. ai

Versions (showing 10 of 10)

Version Deps Published
6.1.3 2 / 0
6.1.2 2 / 0
6.1.1 2 / 0
6.1.0 2 / 0
5.1.1 2 / 0
5.1.0 2 / 0
0.0.4 2 / 0
0.0.3 3 / 0
0.0.2 3 / 0
0.0.1 3 / 0

v6.1.3

1 finding
LOW No provenance attestation provenance

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

v6.1.2

1 finding
INFO No provenance attestation provenance

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

v6.1.1

1 finding
INFO No provenance attestation provenance

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

v6.1.0

1 finding
LOW No provenance attestation provenance

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

v5.1.1

1 finding
INFO No provenance attestation provenance

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

v5.1.0

1 finding
INFO No provenance attestation provenance

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