@atmosx/event-product-parser 3.0.55 → 3.0.62

package/.github/CODE_OF_CONDUCT.md

@@ -1,10 +1,10 @@
-# Code of Conduct
-AtmosphericX is an independent, open source project and is **not** affiliated with, endorsed by, or sponsored by any government agency, meteorological organization, emergency management service, or official weather provider. This project may reference, parse, or process publicly available weather data, including but **not** limited to services operated by the National Weather Service (NWS) and the National Oceanic and Atmospheric Administration (NOAA). All trademarks, service marks, and data rights remain the property of their respective owners. AtmosphericX is provided "as is", without warranty of any kind, express or implied, including but **not** limited to:
-
-- Accuracy or completeness of parsed weather data
-- Fitness for a particular purpose
-- Protection against sources and data retrieval
-- Availability or reliability of upstream data sources
-- Protection against service interruptions or data delays
-
+# Code of Conduct
+AtmosphericX is an independent, open source project and is **not** affiliated with, endorsed by, or sponsored by any government agency, meteorological organization, emergency management service, or official weather provider. This project may reference, parse, or process publicly available weather data, including but **not** limited to services operated by the National Weather Service (NWS) and the National Oceanic and Atmospheric Administration (NOAA). All trademarks, service marks, and data rights remain the property of their respective owners. AtmosphericX is provided "as is", without warranty of any kind, express or implied, including but **not** limited to:
+
+- Accuracy or completeness of parsed weather data
+- Fitness for a particular purpose
+- Protection against sources and data retrieval
+- Availability or reliability of upstream data sources
+- Protection against service interruptions or data delays
+
 AtmosphericX should **not** be relied upon for life safety decisions, emergency response coordination, aviation, marine navigation, or other critical applications. Always consult official sources for authoritative weather information. By using this software, you acknowledge and agree that the maintainers and contributors are **not** liable for any damages, losses, or consequences resulting from its use.

package/.github/CONTRIBUTING.md

@@ -1,30 +1,30 @@
-# Contributing
-
-This project is community driven and primarily maintained by `k3yomi` and `StarflightWx`
-
-## How to Contribute
-
-At this time, contributions are limited to:
-
-- **Corrections** – Fix broken TypeScript syntax, outdated operations, or errors.  
-- **Additions** – Add new functions, tools, or services.  
-- **Clarity Improvements** – Improve explanations in plain English.  
-- **Documentation** – Add helpful content to the documentation.
-
-## What Will Not Be Accepted
-
-- Content that introduces new packages.  
-- Anything that violates GitHub's Terms of Service.
-
-## How to Submit
-
-1. Fork the repository.  
-2. Create a new branch: `fix/description` or `add/description`.  
-3. Make your changes.  
-4. Open a pull request with a clear description of **what changed and why**.
-
-## Requirements
-
-- Use **plain English first, details later**.  
-- Provide **real working examples only** (do not make up syntax).  
+# Contributing
+
+This project is community driven and primarily maintained by `k3yomi`.
+
+## How to Contribute
+
+At this time, contributions are limited to:
+
+- **Corrections** – Fix broken TypeScript syntax, outdated operations, or errors.  
+- **Additions** – Add new functions, tools, or services.  
+- **Clarity Improvements** – Improve explanations in plain English.  
+- **Documentation** – Add helpful content to the documentation.
+
+## What Will Not Be Accepted
+
+- Content that introduces new packages.  
+- Anything that violates GitHub's Terms of Service.
+
+## How to Submit
+
+1. Fork the repository.  
+2. Create a new branch: `fix/description` or `add/description`.  
+3. Make your changes.  
+4. Open a pull request with a clear description of **what changed and why**.
+
+## Requirements
+
+- Use **plain English first, details later**.  
+- Provide **real working examples only** (do not make up syntax).  
 - Follow the existing **file structure and function signature format**.

package/.github/LICENSE

@@ -1,17 +1,17 @@
-Copyright (c) 2026 k3yomi
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
-and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-2. The author of the software must be credited in all copies or substantial portions of the Software, including but not limited to documentation, README files, and source code comments.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Copyright (c) 2026 k3yomi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
+and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+1. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+2. The author of the software must be credited in all copies or substantial portions of the Software, including but not limited to documentation, README files, and source code comments.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/.github/SECURITY.md

@@ -1,21 +1,21 @@
-# Security Policy
-
-## Reporting Vulnerabilities
-If you discover a security vulnerability or issue in this repository such as exposed sensitive data, misconfigurations, or content that could cause harm. Please report it **immediately and responsibly**.  
-
-**Do not report security issues publicly.**  
-Instead, report privately by emailing **antimal@scriptkitty.cafe**, clearly describing the vulnerability.
-
-## What to Include
-When reporting a vulnerability, please include:  
-- A detailed description of the issue  
-- Affected files (include line numbers if possible)  
-- Any recommendations  
-
-## Response
-All reports will be reviewed and addressed as quickly as possible.  
-This is a community driven project, so response times may vary. Please allow up to a few weeks for a full response.  
-
-## Scope
-This repository **does not contain any credentials, keys, tokens, or personally identifiable information (PII)**.  
+# Security Policy
+
+## Reporting Vulnerabilities
+If you discover a security vulnerability or issue in this repository such as exposed sensitive data, misconfigurations, or content that could cause harm. Please report it **immediately and responsibly**.  
+
+**Do not report security issues publicly.**  
+Instead, report privately by emailing **antimal@scriptkitty.cafe**, clearly describing the vulnerability.
+
+## What to Include
+When reporting a vulnerability, please include:  
+- A detailed description of the issue  
+- Affected files (include line numbers if possible)  
+- Any recommendations  
+
+## Response
+All reports will be reviewed and addressed as quickly as possible.  
+This is a community driven project, so response times may vary. Please allow up to a few weeks for a full response.  
+
+## Scope
+This repository **does not contain any credentials, keys, tokens, or personally identifiable information (PII)**.  
 If you discover any such data, report it immediately.