Files
jsonPrism/SECURITY.md
T
poli0981andClaude Opus 5.5 9923c4ce17 chore: 2.2.1 — maintenance mode, Qodana and dependency refresh (#192)
The last release before JSONPrism moves to maintenance mode.

- Dependencies at their latest releases, superseding Dependabot
  #183-#191. i18next 27.1.3, react-i18next 18.0.2 and jsdom 31.0.1 are
  majors; cargo update within semver (wry 0.57.2, tauri-plugin-opener
  2.7.3); sonarqube-scan-action 8.5.0 and setup-java 6.3.0.
  THIRD-PARTY.md is re-synced with both lockfiles.
- Qodana: a new workflow runs Qodana for JS (native mode) and Qodana for
  Rust (EAP, Docker, as root with a bootstrap for the C toolchain and
  GTK/WebKit headers). Both report to Qodana Cloud.
- Qodana findings, all fixed or documented:
  - React types are imported instead of read from the UMD global.
  - XMLBuilder comes from fast-xml-builder; XMLValidator stays, with a
    documented suppression.
  - act() calls in tests are synchronous.
  - The Range geometry test stub is shared.
  - Small regex and boolean cleanups.
  - Two false positives are excluded with their reasons: a secret
    reference, and serde_json, which tauri::generate_context!() needs.
- Maintenance mode:
  - status badge and section in both READMEs;
  - the policy in CONTRIBUTING;
  - converter and translation issue templates;
  - a Scope checklist in the PR template;
  - ROADMAP Phase 11;
  - maintenance-triage.yml closes out-of-scope feature requests with a
    bilingual comment;
  - a Dependabot group for the two fast-xml packages.
- Release 2.2.1: versionCode 20201, CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 18:42:33 +07:00

3.5 KiB

Security policy

Supported versions

JSONPrism follows Semantic Versioning. Only the latest release of the current major version receives security fixes; the website always runs the latest code on main.

Version Supported
2.x ✅
< 2.0 ❌

JSONPrism has been in maintenance mode since 2.2.1. That doesn't change this policy: security fixes keep shipping, and a dependency with a high or critical CVE is fixed as soon as possible.

Reporting a vulnerability

Please do not open a public GitHub Issue for security reports.

Use GitHub's private vulnerability reporting:

→ https://github.com/poli0981/jsonPrism/security/advisories/new

This reaches the maintainer through a private channel. Include a proof of concept, a suggested fix if you have one, and your preferred disclosure timeline.

If you cannot use GitHub, email security@poli0981.dev. The same contacts are published in /.well-known/security.txt.

Response expectations

JSONPrism is a one-person open-source project (see DISCLAIMER.md). Response times are best effort:

Severity Initial response Fix released
Critical (code execution, data exfiltration, supply-chain compromise) within 48 h as soon as possible
High (information disclosure, persistent XSS, CSP bypass) within 7 days next release
Medium / Low within 30 days next minor release

Conversion runs entirely on the user's device, so realistic critical issues are: malicious input that achieves code execution in the browser or the Tauri WebView, a compromised dependency, a converter flaw that produces output dangerous to downstream consumers (for example SQL or CSV injection beyond what the options document), or a weakness in the website's edge configuration.

Scope

In scope:

  • src/ — the React app, converters and batch processor.
  • worker/ — the Cloudflare Worker (per-client rate limits for the whole site, /api/turnstile/verify, /api/health): rate limiting, origin checks, request validation.
  • Website edge configuration: public/_headers (CSP and security headers), public/_redirects, wrangler.jsonc.
  • src-tauri/ — the Rust shell, capabilities, file-system scope and CSP.
  • Build and release tooling whose output ships to users: the website build, Tauri release artifacts and .github/workflows/.

Out of scope:

  • Cloudflare, GitHub Pages or GitHub Actions platform issues — report them to Cloudflare or GitHub.
  • WebView2 / WebKitGTK / WKWebView / Android System WebView bugs — report them to their vendors. JSONPrism uses whatever is installed on the user's system.
  • Turnstile bypasses that only affect Cloudflare's challenge itself.
  • Attacks that require existing local code execution on the user's machine.
  • Missing best-practice headers with no demonstrable impact.

Verifying releases

Every GitHub release includes SHA256SUMS.txt and build-provenance attestations generated in GitHub Actions:

sha256sum -c SHA256SUMS.txt --ignore-missing
gh attestation verify JSONPrism_2.2.1_x64-setup.exe --repo poli0981/jsonPrism

The desktop installers are not yet code-signed, so Windows SmartScreen and macOS Gatekeeper may warn on first launch.

Acknowledgements

Reporters are credited in the published advisory unless they ask otherwise. Contributors of accepted fixes are credited in the release notes.