@tanstack/react-query-devtools
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/umd/index.development.js | AI (source-diff): Standard Rollup UMD bundle output; long lines from SVG paths and build tooling, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/lib/index.prod.js | AI (source-diff): Standard CJS production build output from Rollup. | ai | |
| source-diff | obfuscated-file:build/lib/Logo.js | AI (source-diff): SVG logo component with long path data lines; not obfuscated. | ai | |
| source-diff | obfuscated-file:build/lib/index.prod.mjs | AI (source-diff): Standard ESM production build output from Rollup. | ai | |
| source-diff | obfuscated-file:build/lib/Logo.mjs | AI (source-diff): SVG logo component with long path data lines; not obfuscated. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): v4 branch maintenance release; dormancy is relative to v5 branch activity. | ai |
Versions (showing 100 of 324)
| Version | Deps | Published |
|---|---|---|
| 5.51.3 | 1 / 4 | |
| 5.51.1 | 1 / 4 | |
| 5.50.1 | 1 / 4 | |
| 5.49.2 | 1 / 4 | |
| 5.49.1 | 1 / 4 | |
| 5.49.0 | 1 / 4 | |
| 5.48.0 | 1 / 4 | |
| 5.47.0 | 1 / 4 | |
| 5.45.1 | 1 / 4 | |
| 5.45.0 | 1 / 4 | |
| 5.44.0 | 1 / 4 | |
| 5.40.1 | 1 / 4 | |
| 5.40.0 | 1 / 4 | |
| 5.39.0 | 1 / 4 | |
| 5.38.0 | 1 / 4 | |
| 5.37.1 | 1 / 4 | |
| 5.36.2 | 1 / 4 | |
| 5.36.1 | 1 / 4 | |
| 5.36.0 | 1 / 4 | |
| 5.35.5 | 1 / 4 | |
| 5.35.4 | 1 / 4 | |
| 5.35.1 | 1 / 4 | |
| 5.34.2 | 1 / 4 | |
| 5.34.1 | 1 / 4 | |
| 5.32.1 | 1 / 4 | |
| 5.32.0 | 1 / 4 | |
| 5.31.0 | 1 / 4 | |
| 5.29.2 | 1 / 4 | |
| 5.29.0 | 1 / 4 | |
| 5.28.14 | 1 / 4 | |
| 5.28.13 | 1 / 4 | |
| 5.28.12 | 1 / 4 | |
| 5.28.10 | 1 / 4 | |
| 5.28.9 | 1 / 4 | |
| 5.28.8 | 1 / 4 | |
| 5.28.6 | 1 / 4 | |
| 5.28.4 | 1 / 4 | |
| 5.28.3 | 1 / 4 | |
| 5.28.2 | 1 / 4 | |
| 5.28.0 | 1 / 4 | |
| 5.27.8 | 1 / 4 | |
| 5.27.6 | 1 / 4 | |
| 5.27.5 | 1 / 4 | |
| 5.27.4 | 1 / 4 | |
| 5.27.3 | 1 / 4 | |
| 5.27.1 | 1 / 4 | |
| 5.27.0 | 1 / 4 | |
| 5.26.3 | 1 / 4 | |
| 5.25.0 | 1 / 4 | |
| 5.24.8 | 1 / 4 | |
| 5.24.7 | 1 / 4 | |
| 5.24.6 | 1 / 4 | |
| 5.24.5 | 1 / 4 | |
| 5.24.2 | 1 / 4 | |
| 5.24.1 | 1 / 4 | |
| 5.24.0 | 1 / 4 | |
| 5.23.0 | 1 / 4 | |
| 5.22.2 | 1 / 4 | |
| 5.21.7 | 1 / 4 | |
| 5.21.5 | 1 / 4 | |
| 5.21.4 | 1 / 4 | |
| 5.21.3 | 1 / 4 | |
| 5.21.2 | 1 / 4 | |
| 5.21.0 | 1 / 4 | |
| 5.20.5 | 1 / 4 | |
| 5.20.4 | 1 / 4 | |
| 5.20.3 | 1 / 4 | |
| 5.20.2 | 1 / 4 | |
| 5.20.1 | 1 / 4 | |
| 5.18.1 | 1 / 4 | |
| 5.18.0 | 1 / 4 | |
| 5.17.21 | 1 / 4 | |
| 5.17.19 | 1 / 4 | |
| 5.17.18 | 1 / 4 | |
| 5.17.15 | 1 / 4 | |
| 5.17.14 | 1 / 4 | |
| 5.17.12 | 1 / 4 | |
| 5.17.10 | 1 / 4 | |
| 5.17.9 | 1 / 4 | |
| 5.17.8 | 1 / 4 | |
| 5.17.7 | 1 / 4 | |
| 5.17.5 | 1 / 4 | |
| 5.17.4 | 1 / 4 | |
| 5.17.3 | 1 / 4 | |
| 5.17.1 | 1 / 4 | |
| 5.17.0 | 1 / 4 | |
| 5.15.5 | 1 / 4 | |
| 5.15.4 | 1 / 4 | |
| 5.15.3 | 1 / 4 | |
| 5.15.0 | 1 / 3 | |
| 5.14.7 | 1 / 3 | |
| 5.14.6 | 1 / 3 | |
| 5.14.5 | 1 / 3 | |
| 5.14.2 | 1 / 3 | |
| 5.14.1 | 1 / 3 | |
| 5.14.0 | 1 / 3 | |
| 5.13.5 | 1 / 3 | |
| 5.13.4 | 1 / 3 | |
| 5.13.3 | 1 / 3 | |
| 5.12.2 | 1 / 3 |
v5.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.