We are committed to providing security updates for the following versions of Friendly-Dates:
| Version | Supported |
|---|---|
| 1.0.x | ❌ |
| 2.0.x | ✅ |
We take the security of Friendly-Dates seriously. If you believe you've found a security vulnerability, please follow these steps:
- Do not disclose the vulnerability publicly
- Email us at dynamicinnovativestudio@gmail with:
- A description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Any suggested mitigations if you have them
When you report a vulnerability:
- You'll receive an acknowledgment within 48 hours
- We will investigate and provide a timeline for a fix
- We will keep you informed about the progress
- Once the issue is resolved, we will publicly acknowledge your responsible disclosure (unless you prefer to remain anonymous)
Friendly-Dates is designed to be a secure date formatting library with no external dependencies. However, here are some best practices to ensure secure usage:
- Keep the library updated to the latest version
- Validate all inputs before passing them to the library, especially when dealing with user input
- Avoid exposing raw dates from your database directly through the library to users, as date formatting could potentially reveal sensitive timing information in some contexts
- Use HTTPS when serving applications that include this library
Friendly-Dates is designed with security in mind:
- Zero dependencies - Minimizes supply chain risks
- Strong typing - Reduces the risk of type-related errors
- Input validation - Checks for and safely handles invalid date inputs
- No eval or Function constructors - Does not use dangerous JavaScript constructs
We conduct regular code reviews and dependency audits to ensure the security of the library. Our CI pipeline includes security scanning to catch potential issues early.
Thank you for helping keep Friendly-Dates and its community safe!