jest-canvas-mock
Mock a canvas in your jest tests.
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): jtenner is a known maintainer of jest-canvas-mock since 2019; legitimate transition from atool, confirmed by 5+ years of continued maintenance. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; informational only for an 8-year-old widely-used package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.5.8 | 2 / 13 | |
| 2.5.2 | 2 / 13 | |
| 2.5.1 | 2 / 13 | |
| 2.5.0 | 2 / 13 | |
| 2.4.0 | 2 / 13 | |
| 2.3.1 | 2 / 13 | |
| 2.3.0 | 2 / 12 | |
| 2.2.0 | 2 / 11 | |
| 2.1.2 | 2 / 11 | |
| 2.1.1 | 2 / 11 | |
| 2.1.0 | 2 / 11 | |
| 2.0.0 | 2 / 10 | |
| 1.1.0 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.0.4 | 0 / 5 | |
| 0.0.3 | 0 / 5 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v2.5.8
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.