| Version | Supported |
|---|---|
| 3.0.x | ✅ |
| 2.0.x | ✅ |
| < 2.0 | ❌ |
If you discover a security vulnerability, please report it responsibly:
Do NOT open a public issue.
Instead, email: theyonecodes@gmail.com
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours
- Assessment: Within 1 week
- Fix/patch: Within 2 weeks for critical issues
pkgdrop includes these security measures:
- Atomic installs — Staging directory + commit prevents partial/corrupt installations
- Package registry — JSON database tracks file ownership, prevents conflicts
- Signature verification — GPG signature validation (
.sig,.ascfiles) - Checksum verification — SHA-256, SHA-512, MD5 integrity checks
- Sandbox extraction — bubblewrap/firejail isolation for untrusted archives
- File locking — Prevents concurrent installs
- Quarantine mode — Suspicious archives isolated for review
- Symlink validation — Catches path traversal attacks
- setuid/setgid stripping — Removes privilege escalation bits
- File size limits — Prevents disk fill attacks
- Archive validation — Checks integrity before extraction
- Sudo warnings — Explicit confirmation before elevation
- Hook system — Custom security policies via pre/post install hooks
When using pkgdrop:
- Always review packages before installing
- Use
--dry-runto preview changes - Enable sandbox extraction (default)
- Install jq for full registry and version tracking
- Keep pkgdrop updated
- Report suspicious packages immediately