← Home

jest-jasmine1

npm Repository Homepage
18
Versions
—
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

cpojerdmitriiabramovfbkentaromiura

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from kentaromiura to cpojer reflects the well-documented transition of Jest maintenance to Christoph Pojer at Facebook. cpojer is the canonical Jest maintainer with a strong track record. ai
npm-metadata no-description AI (npm-metadata): jest-jasmine1 is a sub-package of the Jest monorepo; missing description is a consistent pattern across Jest sub-packages and not a malice indicator. ai

Versions (showing 18 of 18)

Version Deps Published
13.2.2 2 / 0
13.2.1 2 / 0
13.1.2 2 / 0
13.1.1 2 / 0
13.1.0 2 / 0
13.0.0 2 / 0
12.1.0 2 / 0
12.0.2 2 / 0
12.0.1 2 / 0
12.0.0 2 / 0
11.0.2 2 / 0
11.0.1 2 / 0
11.0.0 2 / 0
10.0.2 2 / 0
10.0.1 2 / 0
10.0.0 2 / 0
9.0.3 2 / 0
0.0.0 0 / 0

v13.2.2

1 finding
LOW No provenance attestation provenance

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

v13.2.1

1 finding
LOW No provenance attestation provenance

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

v13.1.2

1 finding
LOW No provenance attestation provenance

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

v13.1.1

1 finding
LOW No provenance attestation provenance

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

v13.1.0

1 finding
LOW No provenance attestation provenance

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

v13.0.0

1 finding
LOW No provenance attestation provenance

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

v12.1.0

1 finding
LOW No provenance attestation provenance

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

v12.0.2

1 finding
LOW No provenance attestation provenance

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

v12.0.1

1 finding
LOW No provenance attestation provenance

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

v12.0.0

2 findings
HIGH Publisher changed: kentaromiura → cpojer (on 2016-04-27) provenance

This version was published by a different npm account than previous versions on 2016-04-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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