We are committed to maintaining a secure ecosystem for all Butterfly CSS users. Currently, the following versions receive active security patches and maintenance:
| Version | Status | Security Updates |
|---|---|---|
| v>3 | Maintained | ✅ Active |
Important: Please do not disclose security vulnerabilities through public GitHub issues.
To protect our community, we follow a responsible disclosure process. If you discover a potential security flaw, please report it privately:
- Email: [Your Email Here]
- GitHub Private Advisory: Navigate to the "Security" tab of this repository and select "Report a vulnerability" to submit a private draft.
We acknowledge all reports within 48 hours and will provide a transparent resolution timeline.
To ensure a high level of service, stability, and optimal performance, we monitor site activity. Please be aware of the following:
- Visit Recording: For quality assurance and to improve the user experience, visits to this site may be recorded or logged. This data helps us identify technical bottlenecks and optimize service delivery.
- Statistical Analysis: We use industry-standard tools to track usage patterns (e.g., navigation paths, session duration, and regional traffic) to better understand our users' needs.
- Data Protection: This information is used strictly for internal optimization and to protect our infrastructure from malicious activities. We do not sell or share individual user data with third parties.
- Client-Side Integrity: Butterfly CSS is distributed with integrity checks to ensure that files (via CDN or NPM) are free from malicious injections or unauthorized modifications.
- No Hidden Execution: Our framework is designed to be transparent and lightweight. We do not execute hidden scripts that could compromise your application's security or performance.
Last Updated: April 2026