← Home

@types/es6-collections

npm Repository Homepage

TypeScript definitions for es6-collections

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
email-domain unclaimed-email:http://github.com/rbuckton AI (email-domain): The 'email' is actually a GitHub profile URL used as author contact in an old DefinitelyTyped convention. github.com is a valid, claimed domain — not an exploitable unclaimed email domain. ai
provenance no-provenance AI (provenance): Package is nearly 10 years old and published by the trusted 'types' publisher (DefinitelyTyped). Lack of provenance is expected and not a risk signal here. ai

Versions (showing 10 of 10)

Version Deps Published
0.5.37 0 / 0
0.5.36 0 / 0
0.5.35 0 / 0
0.5.34 0 / 0
0.5.33 0 / 0
0.5.32 0 / 0
0.5.31 0 / 0
0.5.30 0 / 0
0.5.29 0 / 0
0.0.28 0 / 0

v0.5.37

1 finding
LOW No provenance attestation provenance

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

v0.5.36

1 finding
LOW No provenance attestation provenance

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

v0.5.35

1 finding
INFO No provenance attestation provenance

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

v0.5.34

1 finding
INFO No provenance attestation provenance

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

v0.5.33

1 finding
LOW No provenance attestation provenance

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

v0.5.32

1 finding
LOW No provenance attestation provenance

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

v0.5.31

1 finding
INFO No provenance attestation provenance

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

v0.5.30

1 finding
INFO No provenance attestation provenance

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

v0.5.29

1 finding
INFO No provenance attestation provenance

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

v0.0.28

2 findings
HIGH Unclaimed maintainer email domain: http://github.com/rbuckton email-domain

Maintainer email 'http://github.com/rbuckton' uses domain 'http://github.com/rbuckton' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.