@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 395)
| Version | Deps | Published |
|---|---|---|
| 1.8.41 | 16 / 0 | |
| 1.8.40 | 16 / 0 | |
| 1.8.39 | 16 / 0 | |
| 1.8.38 | 16 / 0 | |
| 1.8.37 | 16 / 0 | |
| 1.8.36 | 16 / 0 | |
| 1.8.35 | 16 / 0 | |
| 1.8.34 | 16 / 0 | |
| 1.8.33 | 16 / 0 | |
| 1.8.32 | 16 / 0 | |
| 1.8.31 | 16 / 0 | |
| 1.8.30 | 16 / 0 | |
| 1.8.29 | 16 / 0 | |
| 1.8.28 | 16 / 0 | |
| 1.8.27 | 16 / 0 | |
| 1.8.26 | 16 / 0 | |
| 1.8.25 | 16 / 0 | |
| 1.8.24 | 16 / 0 | |
| 1.8.23 | 16 / 0 | |
| 1.8.22 | 16 / 0 | |
| 1.8.21 | 16 / 0 | |
| 1.8.20 | 16 / 0 | |
| 1.8.19 | 16 / 0 | |
| 1.8.18 | 16 / 0 | |
| 1.8.17 | 16 / 0 | |
| 1.8.16 | 16 / 0 | |
| 1.8.15 | 16 / 0 | |
| 1.8.14 | 16 / 0 | |
| 1.8.13 | 16 / 0 | |
| 1.8.12 | 16 / 0 | |
| 1.8.11 | 16 / 0 | |
| 1.8.10 | 16 / 0 | |
| 1.8.9 | 16 / 0 | |
| 1.8.8 | 16 / 0 | |
| 1.8.7 | 16 / 0 | |
| 1.8.6 | 16 / 0 | |
| 1.8.0 | 16 / 0 | |
| 1.7.26 | 16 / 0 | |
| 1.7.25 | 16 / 0 | |
| 1.7.23 | 16 / 0 | |
| 1.7.22 | 16 / 0 | |
| 1.7.18 | 16 / 0 | |
| 1.7.16 | 16 / 0 | |
| 1.7.15 | 16 / 0 | |
| 1.7.14 | 16 / 0 | |
| 1.7.13 | 16 / 0 | |
| 1.7.12 | 16 / 0 | |
| 1.7.11 | 16 / 0 | |
| 1.7.10 | 16 / 0 | |
| 1.7.9 | 16 / 0 | |
| 1.7.5 | 16 / 0 | |
| 1.7.4 | 16 / 0 | |
| 1.7.3 | 16 / 0 | |
| 1.7.1 | 16 / 0 | |
| 1.7.0 | 16 / 0 | |
| 1.6.22 | 16 / 0 | |
| 1.6.21 | 16 / 0 | |
| 1.6.20 | 16 / 0 | |
| 1.6.19 | 16 / 0 | |
| 1.6.18 | 16 / 0 | |
| 1.6.17 | 16 / 0 | |
| 1.6.16 | 16 / 0 | |
| 1.6.15 | 16 / 0 | |
| 1.6.13 | 16 / 0 | |
| 1.6.12 | 16 / 0 | |
| 1.6.10 | 16 / 0 | |
| 1.6.9 | 16 / 0 | |
| 1.6.8 | 16 / 0 | |
| 1.6.7 | 16 / 0 | |
| 1.6.6 | 16 / 0 | |
| 1.6.5 | 16 / 0 | |
| 1.6.4 | 16 / 0 | |
| 1.6.3 | 16 / 0 | |
| 1.6.2 | 16 / 0 | |
| 1.6.1 | 16 / 0 | |
| 1.6.0 | 16 / 0 | |
| 1.5.0 | 16 / 0 | |
| 1.4.122 | 16 / 0 | |
| 1.4.121 | 16 / 0 | |
| 1.4.119 | 16 / 0 | |
| 1.4.118 | 16 / 0 | |
| 1.4.115 | 16 / 0 | |
| 1.4.113 | 16 / 0 | |
| 1.4.110 | 16 / 0 | |
| 1.4.107 | 16 / 0 | |
| 1.4.106 | 16 / 0 | |
| 1.4.104 | 16 / 0 | |
| 1.4.103 | 16 / 0 | |
| 1.4.99 | 16 / 0 | |
| 1.4.97 | 16 / 0 | |
| 1.4.96 | 16 / 0 | |
| 1.4.94 | 16 / 0 | |
| 1.4.93 | 16 / 0 | |
| 1.4.92 | 16 / 0 | |
| 1.4.90 | 16 / 0 | |
| 1.4.89 | 16 / 0 | |
| 1.4.88 | 16 / 0 | |
| 1.4.86 | 16 / 0 | |
| 1.4.84 | 16 / 0 | |
| 1.4.82 | 16 / 0 |
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.
v1.8.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.