| Version | Status | Notes |
|---|---|---|
| 5.x | Supported | Current release line; security fixes as needed. |
| < 5.0 | Unsupported | Upgrade to the current release for security fixes. |
Do NOT open a public GitHub issue for security vulnerabilities.
- Use GitHub's Report a vulnerability option on the repository's Security tab. If that option is unavailable, contact the maintainer privately through their GitHub profile. Do not include exploit details in a public issue.
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes or patches
Response timeline:
| Step | Target |
|---|---|
| Initial acknowledgement | ≤ 48 hours |
| Triage and severity assessment | ≤ 5 business days |
| Fix or mitigation | ≤ 30 days for critical |
| Public disclosure | After fix is released |
- No hardcoded credentials — never commit passwords, API keys, or tokens
- Input validation — validate all user-supplied values at system boundaries (config dimensions, material names)
- No
eval/ dynamic code — this is a pure-client SPA; avoid any dynamic code execution - Sanitise SVG output — exported SVGs must not embed user-controlled scripts
- Dependabot is configured to open PRs for dependency updates weekly
- Review security advisories before merging dependency updates
- Run
npm auditto check for known vulnerabilities
| Package | Advisory | Severity | Status |
|---|---|---|---|
tmp ≤ 0.2.3 |
GHSA-52f5-9888-hmc6 — symlink write via dir param |
Low | Dev-tool only via @lhci/cli. No safe tmp release exists. WoodworkingShop production build: npm audit reports 0 vulnerabilities. Tracked: awaiting @lhci/cli to drop tmp dependency. |
- No hardcoded credentials or tokens in code
- All user input validated and clamped before use
- No new
eval,Function(), orinnerHTMLwith user content -
npm auditreports no new high/critical issues - Dependencies added are necessary and from trusted sources
Accessibility violations are treated as quality-blocking issues in this project. The following measures ensure WCAG 2.2 AA compliance is maintained:
| Gate | Details |
|---|---|
| axe-core CI | @axe-core/playwright runs on every PR. Any WCAG 2.1 AA violation fails the pipeline with a named assertion error. |
| Lighthouse CI | Performance and accessibility categories are gated via config/lighthouserc.json. categories:accessibility must be ≥ 0.90 (error-level). |
| PR checklist | Contributors are asked to run the app with keyboard-only navigation and a screen reader on any UI change. |
Accessibility barriers that affect users with disabilities are treated as security-equivalent defects — they restrict access and can violate applicable law (e.g. WCAG, ADA, EN 301 549).
- Report via a public GitHub issue tagged
accessibility(unlike security vulnerabilities, a11y issues may be reported publicly) - Include: browser/OS, assistive technology used, steps to reproduce, WCAG criterion affected
- Target resolution: ≤ 14 days for Level A violations, ≤ 30 days for Level AA