Skip to content

Latest commit

 

History

History
100 lines (72 loc) · 5.73 KB

SECURITY.md

File metadata and controls

100 lines (72 loc) · 5.73 KB

Security policy

Updates

The project's latest version published to the npm registry.

Always use the latest version of @stassi/leaf via the npm update command (documentation) to ensure the latest security updates are received.

Reporting

If you discover a potential vulnerability in the @stassi/leaf codebase, please follow these steps:

  1. Do not publicly disclose any potential vulnerability. Public disclosure increases the risk of a malicious exploit before a remedy is available.

  2. Contact [email protected] directly via email. Please provide detailed information about the potential vulnerability, including steps to reproduce and any relevant code snippets or logs. Additional information or clarification may be requested.

Maintenance

Displays the pass-fail status of the project's automated security scans via GitHub Actions.

Automated security scans are integrated into the continuous delivery (CD) pipeline.

Advisories

View all security advisories for @stassi/leaf.

Dependencies

Dependabot, Snyk, and the npm audit command (documentation) mitigate upstream security risks by analyzing upstream dependencies. Potential vulnerabilities in third-party libraries like Leaflet are patched during the build process.

Sanitization

All dynamic HTML content is sanitized using DOMPurify to prevent cross-site scripting (XSS) attacks.

Static analysis

CodeQL (Semmle) and ESLint use static analysis to detect potential vulnerabilities early.

Disclosures

The following potential vulnerabilities were resolved after detection.

DOM clobbering gadget in rollup bundled scripts leading to XSS

Regular expression denial of service (ReDoS) in path-to-regexp

Regular expression denial of service (ReDoS) in cross-spawn

Unsafe HTML constructed from leaflet library input