react-query
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/react-query-devtools.development.js | AI (source-diff): Rollup UMD build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:es/devtools/Logo.js | AI (source-diff): Long line is an inline SVG path in the Logo component. | ai | |
| source-diff | obfuscated-file:lib/devtools/Logo.js | AI (source-diff): Long line is an inline SVG path in the Logo component. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo dist package; missing README/keywords is expected and not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; absence is not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.39.3 | 3 / 55 | |
| 3.5.3 | 2 / 52 | |
| 3.3.0 | 2 / 52 | |
| 3.2.0 | 2 / 52 | |
| 3.1.1 | 1 / 52 | |
| 3.1.0 | 1 / 52 |
v3.5.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.