@thisisagile/easy-test-react
Straightforward wrapper library for testing-library/react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer/framework dep declared for consumers; not directly imported by the library itself. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only framework dep; loaded by convention, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@testing-library/dom | AI (phantom-deps): Transitive testing-library dep; loaded by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@testing-library/jest-dom | AI (phantom-deps): Testing framework dep loaded by convention; stable false positive for this package. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 18.4.0 | 7 / 3 | |
| 18.3.0 | 7 / 3 | |
| 18.2.0 | 7 / 3 | |
| 18.1.2 | 7 / 3 | |
| 18.1.1 | 7 / 3 | |
| 18.1.0 | 7 / 3 | |
| 18.0.1 | 7 / 3 | |
| 18.0.0 | 7 / 3 | |
| 17.36.0 | 7 / 3 | |
| 17.35.0 | 7 / 3 | |
| 17.34.4 | 7 / 3 | |
| 17.34.3 | 7 / 3 | |
| 17.34.2 | 7 / 3 | |
| 17.34.1 | 7 / 3 | |
| 17.34.0 | 7 / 3 | |
| 17.33.0 | 7 / 3 | |
| 17.32.0 | 7 / 3 | |
| 17.31.1 | 7 / 3 | |
| 17.31.0 | 7 / 3 | |
| 17.30.11 | 7 / 3 | |
| 17.30.10 | 7 / 3 | |
| 17.30.9 | 7 / 3 | |
| 17.30.8 | 7 / 3 | |
| 17.30.7 | 7 / 3 | |
| 17.30.6 | 7 / 3 | |
| 17.30.5 | 7 / 3 | |
| 17.30.4 | 7 / 3 | |
| 17.30.3 | 7 / 3 | |
| 17.30.2 | 7 / 3 | |
| 17.30.1 | 7 / 3 | |
| 17.30.0 | 7 / 3 | |
| 17.29.0 | 7 / 3 | |
| 17.28.0 | 7 / 3 | |
| 17.27.3 | 7 / 3 | |
| 17.27.2 | 7 / 3 | |
| 17.27.1 | 7 / 3 | |
| 17.27.0 | 7 / 3 | |
| 17.26.4 | 7 / 3 | |
| 17.26.3 | 7 / 3 | |
| 17.26.2 | 7 / 3 | |
| 17.26.1 | 7 / 3 | |
| 17.26.0 | 7 / 3 | |
| 17.25.3 | 7 / 3 | |
| 17.25.2 | 7 / 3 | |
| 17.25.1 | 7 / 3 | |
| 17.25.0 | 7 / 3 | |
| 17.24.3 | 7 / 3 | |
| 17.24.2 | 7 / 3 | |
| 17.24.1 | 7 / 3 | |
| 17.24.0 | 7 / 3 | |
| 17.23.1 | 7 / 3 |
v18.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.30.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.