jquery
JavaScript library for DOM operations
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): timmywil is a long-standing jQuery core team member; mgol→timmywil is a known legitimate maintainer transition within the jQuery project. | ai | |
| provenance | no-provenance | AI (provenance): jQuery 3.x versions predate npm Sigstore provenance support; absence is expected for this era of releases. | ai | |
| phantom-deps | phantom-dep:npm | AI (phantom-deps): npm is used in build scripts (package.json scripts field), not as a library import. Phantom dep finding is a false positive for build tooling declared in dependencies by mistake. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is used in build/release scripts, not imported as a library dependency. Phantom dep finding is a false positive for build tooling. | ai | |
| phantom-deps | phantom-dep:shelljs | AI (phantom-deps): shelljs is used in build/release scripts, not imported as a library dependency. Phantom dep finding is a false positive for build tooling. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): archiver is used in build/release scripts, not imported as a library dependency. Phantom dep finding is a false positive for build tooling. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 0 / 0 | |
| 3.7.1 | 0 / 42 | |
| 3.7.0 | 0 / 41 | |
| 3.6.4 | 0 / 40 | |
| 3.6.3 | 0 / 40 | |
| 3.6.2 | 0 / 41 | |
| 3.6.1 | 0 / 41 | |
| 3.6.0 | 0 / 40 | |
| 3.5.1 | 0 / 40 | |
| 3.5.0 | 0 / 40 | |
| 2.2.4 | 0 / 24 | |
| 2.2.3 | 0 / 24 | |
| 2.2.2 | 0 / 24 | |
| 2.2.1 | 0 / 24 | |
| 2.2.0 | 0 / 24 | |
| 2.1.4 | 0 / 16 | |
| 2.1.3 | 0 / 16 | |
| 2.1.2 | 0 / 15 | |
| 2.1.1 | 0 / 15 | |
| 2.1.0 | 0 / 16 | |
| 1.12.4 | 0 / 25 | |
| 1.12.3 | 0 / 25 | |
| 1.12.2 | 0 / 25 | |
| 1.12.1 | 0 / 25 | |
| 1.12.0 | 0 / 25 | |
| 1.11.3 | 0 / 15 | |
| 1.11.2 | 0 / 15 | |
| 1.11.1 | 0 / 15 | |
| 1.11.0 | 0 / 16 | |
| 1.9.1 | 0 / 8 | |
| 1.8.3 | 6 / 2 | |
| 1.8.2 | 5 / 2 | |
| 1.7.3 | 5 / 2 | |
| 1.7.2 | 3 / 2 | |
| 1.6.3 | 2 / 0 | |
| 1.6.2 | 2 / 0 | |
| 4.0.0-rc.2 | 0 / 0 | |
| 4.0.0-rc.1 | 0 / 0 |
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
2 findingsThis version was published by a different npm account than previous versions on 2020-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-10. This could indicate a legitimate maintainer transition or an account compromise.