Security
REPORT SECURITY ISSUES WITHOUT PUBLISHING THE EXPLOIT.
Glyphic is still establishing its formal security process. Do not place credentials, private user data, or exploit details in a public issue.
Responsible reporting
MINIMIZE EXPOSURE WHILE THE REPORTING CHANNEL MATURES.
Use the repository's published security guidance if present. If no private channel is documented, open a minimal public issue asking for a secure contact without including sensitive detail.
- Do not test against data you do not own
- Do not publish secrets or personal information
- Allow reasonable time for investigation
No false assurances
THIS PAGE DOES NOT CLAIM CERTIFICATIONS OR AUDITS.
Security claims will be added only when supported by actual process, evidence, and review.
KEEP YOUR SOURCES CLOSE AND YOUR IDEAS MOVING.
Glyphic is being built in the open. Begin with the current product, follow the work, and help make the system more useful.