Versioned security assessment
Report ID: SA-A0668140
7/6/2026, 3:01:22 PM
tanstack-query security assessment v3
Skill Security Certification Report
Audit model: codex Historical report
- Skill name
- tanstack-query
- Version
- v3
- Maintainer
- jezweb
- Coverage
- 22 Files scanned · 4,893 Lines analyzed
- Policy version
- Unavailable
Highest confirmed finding severity
Medium
2 confirmed security findings require attention.
Installation context
Historical evidence
This report may not describe the currently installable artifact. Open the current Skill page for install guidance.
Open current Skill pageThis report does not block or authorize the manifest or ZIP.
Most static findings are false positives caused by Markdown backticks, TypeScript template literals, local API examples, and React identifiers. Confirmed issues are low-risk external demo API calls in copy-ready templates, plus medium-risk semantic concerns around production DevTools exposure and visible stack traces.
Report position
Historical report
Open audit history before using this report to install.
Audit attestation
Not attestable
The required immutable binding is incomplete.
Human verification
Not verified
No human verification is recorded for this report.
Coverage
22 Files scanned · 4,893 Lines analyzed
30 items shown for review
Limitations
This report does not claim runtime or sandbox execution and does not prove the absence of side effects.
Evidence chain
Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.
Source
Binding unavailable
Artifact
Identity incomplete
Audit
Complete
Capabilities observed
Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.
Contains scripts
May execute code included with the Skill.
Observed in 1 evidence location
Network access
May connect to external services.
Observed in 57 evidence locations
Filesystem access
May read or write local files.
Not recorded by this audit
Env variables
May read values from the process environment.
Not recorded by this audit
External commands
May invoke commands or programs outside the Skill.
Observed in 212 evidence locations
Capability review items (28)
Low
Fetch API call
const response = await fetch('https://jsonplaceholder.typicode.com/users')
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`)
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch('https://jsonplaceholder.typicode.com/users', {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`, {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`, {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch('https://jsonplaceholder.typicode.com/users')
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`)
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch('https://jsonplaceholder.typicode.com/users', {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`, {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch(`https://jsonplaceholder.typicode.com/users/${id}`, {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos?_start=${start}&_limit=${limit}`
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch('https://jsonplaceholder.typicode.com/todos', {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch('https://jsonplaceholder.typicode.com/todos', {
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos/${id}`,
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos/${id}`,
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
'https://jsonplaceholder.typicode.com/todos',
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos/${id}`,
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos/${id}`,
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch('https://jsonplaceholder.typicode.com/todos')
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Fetch API call
const response = await fetch(
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
const response = await fetch('https://jsonplaceholder.typicode.com/todos')
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Low
Hardcoded URL
`https://jsonplaceholder.typicode.com/todos/${id}`
This copy-ready template calls the public jsonplaceholder API. It is not malicious, but users could accidentally send entered sample data to an external third-party service if run unchanged.
Risk findings
Confirmed security concerns are separated from items that still need review.
Confirmed security concerns (2)
RISK-001 Medium
Production DevTools Can Expose Cache Data
The production DevTools example loads and renders React Query DevTools when a local showDevTools flag is true, but the sample does not enforce authentication. Query cache data can include user records, tokens, or API responses if copied into production.
The file explicitly labels the section as production DevTools and renders the component from a local toggle only. The same file later warns not to ship production DevTools without authentication.
RISK-002 Medium
Error Boundary Displays Stack Traces
The default fallback renders error.message and error.stack in the page. Production users could see implementation details if this template is copied without an environment guard.
The code directly renders error details and the stack trace inside the visible fallback UI. This is useful during development but can leak internal details in production.
Remediation
Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.
- FIX-001MediumProduction DevTools example lacks an enforced auth gate.Wrap production DevTools behind role-based authentication and a server-controlled feature flag, or remove the production example from copy-ready templates.
- FIX-002MediumDefault error boundary can expose stack traces to users.Show generic production errors in the UI and send stack traces only to a trusted error reporting service.
- FIX-003LowCopy-ready templates use public demo API endpoints.Use placeholder base URLs or local mock handlers, and clearly require endpoint replacement before using real data.
- FIX-004LowPlaceholder shell script ships with the skill.Remove the unused script or document that it is nonfunctional, so installers do not see an unnecessary executable artifact.
Expert evidence
Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.
Artifact subject
- Marketplace commit
- Unavailable
- Content hash
- Unavailable
- Tree hash
- Unavailable
- Skill path
- Unavailable
- Audit payload hash
- Unavailable
Analysis metadata
Audit model: codex
Analysis state: Complete
Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.
Verify and export
The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.
Audit attestation: not_attestable