-
Notifications
You must be signed in to change notification settings - Fork 1
SECURITY
github-actions[bot] edited this page May 29, 2026
·
1 revision
| Version | Supported |
|---|---|
| 1.x (latest) | Yes |
| < 1.0 | No |
moon-sighting is a pure astronomical computation library. It accepts observer coordinates and a date as input and returns visibility predictions. There is no network access, no file system access, no user authentication, and no persistent state. The JPL DE442S ephemeris data is bundled as a static binary blob.
Security vulnerabilities are unlikely given the surface area. That said, if you find something:
- Do not open a public issue. That exposes the vulnerability before a fix is available.
- Email aric.camarata@gmail.com with the subject line "Security: moon-sighting".
- Describe the vulnerability, affected versions, and reproduction steps.
- You will receive a response within 7 days.
- An input that causes the library to execute arbitrary code
- A dependency with a known CVE that affects this package's behavior
- Prototype pollution via user-provided inputs
- Buffer overflow or memory corruption in the ephemeris parsing code
- Incorrect crescent visibility predictions (that is a bug, not a security issue)
- Missing input validation that causes incorrect output but no code execution
moon-sighting · MIT License · npm · Issues
Guides
Examples
API Reference
- getMoonSightingReport
- getMoonPhase
- getMoonPosition
- getMoonIllumination
- getMoonVisibilityEstimate
- getMoon
- getSunMoonEvents
- initKernels
- downloadKernels
- verifyKernels
Domain Reference
Package Reference
Community