← Home

tough-cookie

npm Repository Homepage

RFC6265 Cookies and Cookie Jar for node.js

8
Versions
BSD-3-Clause
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

awatermaccasey

Keywords

HTTPcookiecookiesset-cookiecookiejarjarRFC6265RFC2965

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation, indicating intentional CI/CD publishing transition for salesforce/tough-cookie. This pattern is expected to continue. ai
publish-pattern dormant-publish AI (publish-pattern): Mature library with infrequent releases; SLSA attestation confirms legitimate CI/CD publish, ruling out account takeover during dormancy. ai
dependencies unvetted-dep:tldts AI (dependencies): tldts is a well-established TLD parsing library appropriate for a cookie library; its use here is expected and legitimate for RFC6265 domain validation. ai

Versions (showing 8 of 8)

Version Deps Published
6.0.1 1 / 18
6.0.0 1 / 18
5.1.2 1 / 20
5.1.1 1 / 20
5.1.0 1 / 18
5.0.0 1 / 18
4.1.4 4 / 8
4.1.3 4 / 8

v6.0.0

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.

v5.1.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.

v5.1.0

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.

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.1.4

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.

v4.1.3

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.