We release patches for security vulnerabilities in the following versions:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
If you discover a security vulnerability in StyleInspectorKit, please report it responsibly:
- Do not open a public issue
- Email security details to: [abtahi.7cgen@gmail.com]
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- We will acknowledge receipt within 48 hours
- We will provide regular updates on our progress
- We will credit you in our security advisories (unless you prefer to remain anonymous)
- Local Processing: All analysis happens locally in your browser
- No Data Collection: We don't collect or transmit any personal data
- No Tracking: Zero analytics or user tracking
- Minimal Permissions: Only requests necessary Chrome extension permissions
StyleInspectorKit requests minimal permissions:
activeTab: To analyze the current webpagescripting: To inject content scripts for analysisstorage: To store user preferences locally
- All extracted data stays on your device
- No data is sent to external servers
- User preferences are stored locally using Chrome's storage API
- No cookies or tracking mechanisms
- Keep Chrome browser updated
- Only install extensions from trusted sources
- Review extension permissions before installation
- Report suspicious behavior immediately
- Follow Chrome extension security guidelines
- Use Content Security Policy (CSP)
- Validate all user inputs
- Keep dependencies updated
- Use secure coding practices
For security-related questions or concerns, please contact:
- Email: [abtahi.7cgen@gmail.com]
- GitHub Issues: For non-security bugs and feature requests
Note: This security policy is subject to change. Please check back regularly for updates.