The project is actively maintained on the main branch.
| Version/Branch | Supported |
|---|---|
main (latest) |
Yes |
| Older commits/releases | No |
If you are running an older deployment, upgrade to the latest main before reporting behavior that may already be fixed.
Please use GitHub Private Vulnerability Reporting for security issues.
- Repository:
arnoldcho/xpchain-web - Preferred channel: Security tab -> "Report a vulnerability"
If private reporting is unavailable, contact maintainers through a private channel and include:
- Affected endpoint/path/component
- Reproduction steps
- Expected vs actual behavior
- Impact assessment (confidentiality/integrity/availability)
- Proof of concept (minimal)
- Suggested fix (optional)
Do not open public issues for unpatched vulnerabilities.
Target response times:
- Initial acknowledgement: within 72 hours
- Triage decision: within 7 days
- Fix timeline: based on severity and exploitability
Coordinated disclosure is required.
- Maintainers validate and patch first
- Security advisory/release note is published after mitigation
- Credit is provided to the reporter unless anonymity is requested
In scope:
- Application routes under
app/ - API routes under
app/api/ - Authentication/authorization or data-exposure issues
- Dependency vulnerabilities with practical exploit path
Out of scope (unless chained with real impact):
- Best-practice suggestions without exploitability
- Social engineering or phishing scenarios
- Denial-of-service requiring unrealistic resources
Good-faith research is welcomed.
Please avoid:
- Accessing/modifying user or production data
- Service disruption
- Public disclosure before coordinated resolution