← Home

axios-cookiejar-support

Add tough-cookie support to axios.

46
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

3846masa

Keywords

axioscookiecookiejarcookiestough-cookie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transition from manual publish to GitHub Actions CI/CD with SLSA provenance; repo unchanged. ai

Versions (showing 46 of 46)

Version Deps Published
7.0.0 1 / 15
6.0.5 1 / 16
6.0.4 1 / 16
6.0.3 1 / 18
6.0.2 1 / 18
6.0.1 1 / 18
6.0.0 1 / 18
5.0.5 1 / 18
5.0.4 1 / 18
5.0.3 1 / 19
5.0.2 1 / 19
5.0.1 1 / 18
5.0.0 1 / 14
4.0.7 1 / 14
4.0.6 1 / 14
4.0.5 1 / 14
4.0.4 1 / 13
4.0.3 1 / 13
4.0.2 1 / 13
4.0.1 1 / 13
4.0.0 1 / 13
3.0.0 1 / 11
2.0.5 1 / 11
2.0.4 1 / 11
2.0.3 1 / 11
2.0.2 1 / 11
2.0.1 1 / 11
2.0.0 1 / 11
1.0.1 2 / 16
1.0.0 2 / 16
0.5.1 4 / 15
0.5.0 4 / 5
0.4.2 4 / 13
0.4.1 4 / 13
0.4.0 4 / 13
0.3.6 4 / 13
0.3.5 4 / 13
0.3.4 4 / 13
0.3.3 3 / 13
0.3.2 3 / 13
0.3.1 3 / 13
0.3.0 3 / 13
0.2.1 3 / 14
0.2.0 3 / 14
0.1.4 3 / 8
0.1.3 3 / 11

v7.0.0

2 findings
HIGH Publisher changed: 3846masa → GitHub Actions (on 2026-05-06) provenance

This version was published by a different npm account than previous versions on 2026-05-06. This could indicate a legitimate maintainer transition or an account compromise.

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.

v6.0.5

1 finding
LOW No provenance attestation provenance

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

v6.0.4

1 finding
LOW No provenance attestation provenance

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

v6.0.3

1 finding
LOW No provenance attestation provenance

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

v6.0.2

1 finding
LOW No provenance attestation provenance

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

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.0.5

1 finding
LOW No provenance attestation provenance

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

v5.0.4

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

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.