@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 24 of 324)
| Version | Deps | Published |
|---|---|---|
| 5.12.1 | 1 / 3 | |
| 5.12.0 | 1 / 3 | |
| 5.10.0 | 1 / 3 | |
| 5.9.0 | 1 / 6 | |
| 5.8.9 | 1 / 6 | |
| 5.8.8 | 1 / 6 | |
| 5.8.7 | 1 / 6 | |
| 5.8.6 | 1 / 6 | |
| 5.8.4 | 1 / 6 | |
| 5.8.3 | 1 / 6 | |
| 5.8.2 | 1 / 6 | |
| 5.8.1 | 1 / 6 | |
| 5.7.4 | 1 / 6 | |
| 5.7.2 | 1 / 6 | |
| 5.7.1 | 1 / 6 | |
| 5.7.0 | 1 / 6 | |
| 5.4.3 | 1 / 6 | |
| 5.4.2 | 1 / 6 | |
| 5.1.0 | 1 / 6 | |
| 5.0.5 | 1 / 6 | |
| 5.0.3 | 1 / 6 | |
| 5.0.1 | 1 / 6 | |
| 5.0.0 | 1 / 6 | |
| 4.44.0 | 3 / 11 |
v5.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.