@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 100 of 377)
| Version | Deps | Published |
|---|---|---|
| 1.10.21 | 13 / 0 | |
| 1.10.20 | 13 / 0 | |
| 1.10.19 | 13 / 0 | |
| 1.10.18 | 13 / 0 | |
| 1.10.17 | 13 / 0 | |
| 1.10.16 | 13 / 0 | |
| 1.10.15 | 13 / 0 | |
| 1.10.14 | 13 / 0 | |
| 1.10.13 | 13 / 0 | |
| 1.10.12 | 13 / 0 | |
| 1.10.11 | 13 / 0 | |
| 1.10.10 | 13 / 0 | |
| 1.10.9 | 13 / 0 | |
| 1.10.8 | 13 / 0 | |
| 1.10.7 | 13 / 0 | |
| 1.10.6 | 13 / 0 | |
| 1.10.4 | 13 / 0 | |
| 1.10.3 | 13 / 0 | |
| 1.10.2 | 13 / 0 | |
| 1.10.1 | 13 / 0 | |
| 1.10.0 | 13 / 0 | |
| 1.9.8 | 13 / 0 | |
| 1.9.7 | 13 / 0 | |
| 1.9.6 | 13 / 0 | |
| 1.9.5 | 13 / 0 | |
| 1.9.4 | 13 / 0 | |
| 1.9.3 | 13 / 0 | |
| 1.9.2 | 13 / 0 | |
| 1.9.1 | 13 / 0 | |
| 1.8.117 | 13 / 0 | |
| 1.8.116 | 13 / 0 | |
| 1.8.115 | 13 / 0 | |
| 1.8.114 | 13 / 0 | |
| 1.8.113 | 13 / 0 | |
| 1.8.112 | 13 / 0 | |
| 1.8.111 | 13 / 0 | |
| 1.8.110 | 13 / 0 | |
| 1.8.109 | 13 / 0 | |
| 1.8.108 | 13 / 0 | |
| 1.8.107 | 13 / 0 | |
| 1.8.105 | 13 / 0 | |
| 1.8.103 | 13 / 0 | |
| 1.8.102 | 13 / 0 | |
| 1.8.101 | 13 / 0 | |
| 1.8.100 | 13 / 0 | |
| 1.8.99 | 13 / 0 | |
| 1.8.98 | 13 / 0 | |
| 1.8.97 | 13 / 0 | |
| 1.8.96 | 13 / 0 | |
| 1.8.95 | 13 / 0 | |
| 1.8.94 | 13 / 0 | |
| 1.8.92 | 13 / 0 | |
| 1.8.91 | 13 / 0 | |
| 1.8.90 | 13 / 0 | |
| 1.8.88 | 13 / 0 | |
| 1.8.87 | 13 / 0 | |
| 1.8.86 | 13 / 0 | |
| 1.8.85 | 13 / 0 | |
| 1.8.84 | 13 / 0 | |
| 1.8.83 | 13 / 0 | |
| 1.8.82 | 13 / 0 | |
| 1.8.81 | 13 / 0 | |
| 1.8.80 | 13 / 0 | |
| 1.8.79 | 13 / 0 | |
| 1.8.78 | 13 / 0 | |
| 1.8.77 | 13 / 0 | |
| 1.8.76 | 13 / 0 | |
| 1.8.75 | 14 / 0 | |
| 1.8.74 | 14 / 0 | |
| 1.8.73 | 14 / 0 | |
| 1.8.72 | 14 / 0 | |
| 1.8.71 | 14 / 0 | |
| 1.8.70 | 14 / 0 | |
| 1.8.69 | 14 / 0 | |
| 1.8.68 | 14 / 0 | |
| 1.8.67 | 14 / 0 | |
| 1.8.66 | 14 / 0 | |
| 1.8.65 | 14 / 0 | |
| 1.8.64 | 14 / 0 | |
| 1.8.63 | 14 / 0 | |
| 1.8.61 | 14 / 0 | |
| 1.8.60 | 13 / 0 | |
| 1.8.58 | 13 / 0 | |
| 1.8.57 | 13 / 0 | |
| 1.8.56 | 13 / 0 | |
| 1.8.55 | 13 / 0 | |
| 1.8.53 | 13 / 0 | |
| 1.8.52 | 16 / 0 | |
| 1.8.51 | 16 / 0 | |
| 1.8.50 | 16 / 0 | |
| 1.8.49 | 16 / 0 | |
| 1.8.48 | 16 / 0 | |
| 1.8.45 | 16 / 0 | |
| 1.8.44 | 16 / 0 | |
| 1.8.43 | 16 / 0 | |
| 1.8.42 | 16 / 0 | |
| 1.8.41 | 16 / 0 | |
| 1.8.40 | 16 / 0 | |
| 1.8.39 | 16 / 0 | |
| 1.8.38 | 16 / 0 |
v1.10.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.