DO NOT create a public issue for security vulnerabilities.
Security issues can be responsibly disclosed by emailing:
security@pitanga.org
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if known)
- Your contact information for follow-up
For sensitive reports, you can encrypt your message using our public key:
-----BEGIN AGE PUBLIC KEY-----
age1y8f8qk0h2qjq7q6q5q4q3q2q1q0q9q8q7q6q5q4q3q2q1q0q9q8q7q6q5q4q3q2q1q0q9q8
-----END AGE PUBLIC KEY-----
- Acknowledgment: We will acknowledge receipt within 48 hours
- Investigation: Our security team will investigate and validate the report
- Patch Development: We will develop a fix and test it thoroughly
- Release: We will release a patched version
- Disclosure: We will coordinate public disclosure with the reporter
We provide security updates for the following versions:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| 0.x.x | ✅ |
- Keep your
ageprivate key secure and backed up - Use strong, unique passwords for encrypted files
- Regularly update to the latest version
- Review plugin permissions before installation
- Monitor audit logs for suspicious activity
- Follow secure coding practices
- Never commit secrets or credentials
- Use the vault's encryption methods for any credential storage
- Validate all user input
- Write tests for security-critical code
- Uses
age(Actually Good Encryption) for modern, auditable encryption - Public-key cryptography for key management
- Secure memory handling with
mlock()when available - RAM-backed temporary files
Nakimi assumes:
- The user's machine is not compromised
- The
ageimplementation is secure - Plugins are from trusted sources
- Users follow security best practices
- Not designed for multi-user environments
- Does not protect against compromised host systems
- Requires manual key backup
- Plugin security depends on plugin implementation
Security updates are released as patch versions (e.g., 1.0.0 → 1.0.1). We recommend:
- Subscribing to security announcements
- Enabling automatic updates where possible
- Regularly checking for updates
We welcome security audits from reputable security researchers. Please contact us before starting an audit to coordinate.
We credit security researchers who responsibly disclose vulnerabilities in our security advisories.
For security-related inquiries: security@pitanga.org
Last updated: 2026-02-01