@trackunit/react-test-setup
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): Config-file reference in test setup package; stable pattern. | ai | |
| phantom-deps | phantom-dep:web-streams-polyfill | AI (phantom-deps): Config-file reference in test setup package; stable pattern. | ai | |
| dependencies | unvetted-dep:@okta/okta-react | AI (dependencies): Legitimate Okta SDK used for auth mocking in test setup; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:@okta/okta-auth-js | AI (phantom-deps): Peer/transitive dep referenced in config; not a real phantom-dep concern for this test-setup package. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): Well-known animation library; stable false positive for this test-setup package. | ai | |
| dependencies | unvetted-dep:@googlemaps/jest-mocks | AI (dependencies): Official Google Maps jest mocks library; expected dependency for a test-setup package. | ai | |
| phantom-deps | phantom-dep:react-virtualized-auto-sizer | AI (phantom-deps): react-virtualized-auto-sizer is a declared dep used in config/setup files; stable false positive for this test-setup package. | ai |
Versions (showing 89 of 397)
| Version | Deps | Published |
|---|---|---|
| 1.3.11 | 16 / 0 | |
| 1.3.10 | 16 / 0 | |
| 1.3.6 | 16 / 0 | |
| 1.3.5 | 16 / 0 | |
| 1.3.4 | 16 / 0 | |
| 1.3.3 | 16 / 0 | |
| 1.3.0 | 16 / 0 | |
| 1.2.8 | 16 / 0 | |
| 1.2.7 | 16 / 0 | |
| 1.2.6 | 16 / 0 | |
| 1.2.5 | 16 / 0 | |
| 1.2.0 | 16 / 0 | |
| 1.1.40 | 16 / 0 | |
| 1.1.39 | 16 / 0 | |
| 1.1.38 | 16 / 0 | |
| 1.1.37 | 16 / 0 | |
| 1.1.35 | 16 / 0 | |
| 1.1.34 | 16 / 0 | |
| 1.1.31 | 16 / 0 | |
| 1.1.29 | 16 / 0 | |
| 1.1.28 | 16 / 0 | |
| 1.1.26 | 16 / 0 | |
| 1.1.25 | 16 / 0 | |
| 1.1.24 | 16 / 0 | |
| 1.1.23 | 16 / 0 | |
| 1.1.21 | 16 / 0 | |
| 1.1.20 | 16 / 0 | |
| 1.1.19 | 16 / 0 | |
| 1.1.18 | 16 / 0 | |
| 1.1.17 | 16 / 0 | |
| 1.1.16 | 16 / 0 | |
| 1.1.15 | 16 / 0 | |
| 1.1.14 | 16 / 0 | |
| 1.1.13 | 16 / 0 | |
| 1.1.12 | 16 / 0 | |
| 1.1.10 | 16 / 0 | |
| 1.1.9 | 16 / 0 | |
| 1.1.8 | 16 / 0 | |
| 1.1.7 | 16 / 0 | |
| 1.1.6 | 16 / 0 | |
| 1.1.5 | 16 / 0 | |
| 1.1.4 | 16 / 0 | |
| 1.1.1 | 16 / 0 | |
| 1.1.0 | 16 / 0 | |
| 1.0.56 | 16 / 0 | |
| 1.0.55 | 16 / 0 | |
| 1.0.54 | 16 / 0 | |
| 1.0.53 | 16 / 0 | |
| 1.0.52 | 16 / 0 | |
| 1.0.50 | 16 / 0 | |
| 1.0.49 | 16 / 0 | |
| 1.0.48 | 16 / 0 | |
| 1.0.47 | 16 / 0 | |
| 1.0.45 | 16 / 0 | |
| 1.0.44 | 16 / 0 | |
| 1.0.43 | 16 / 0 | |
| 1.0.41 | 16 / 0 | |
| 1.0.40 | 16 / 0 | |
| 1.0.38 | 16 / 0 | |
| 1.0.37 | 16 / 0 | |
| 1.0.36 | 16 / 0 | |
| 1.0.35 | 16 / 0 | |
| 1.0.34 | 16 / 0 | |
| 1.0.32 | 16 / 0 | |
| 1.0.31 | 16 / 0 | |
| 1.0.30 | 16 / 0 | |
| 1.0.29 | 16 / 0 | |
| 1.0.23 | 13 / 0 | |
| 1.0.22 | 13 / 0 | |
| 1.0.21 | 13 / 0 | |
| 1.0.20 | 13 / 0 | |
| 1.0.19 | 13 / 0 | |
| 1.0.18 | 13 / 0 | |
| 1.0.17 | 13 / 0 | |
| 1.0.16 | 13 / 0 | |
| 1.0.15 | 13 / 0 | |
| 1.0.14 | 13 / 0 | |
| 1.0.13 | 13 / 0 | |
| 1.0.12 | 13 / 0 | |
| 1.0.11 | 13 / 0 | |
| 1.0.10 | 13 / 0 | |
| 1.0.9 | 13 / 0 | |
| 1.0.8 | 13 / 0 | |
| 1.0.7 | 13 / 0 | |
| 1.0.6 | 13 / 0 | |
| 1.0.4 | 13 / 0 | |
| 1.0.3 | 13 / 0 | |
| 1.0.2 | 13 / 0 | |
| 1.0.0 | 13 / 0 |
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.