@omss/core 0.0.2-beta.2 → 0.0.2-beta.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +18 -16
  2. package/SECURITY.md +39 -0
  3. package/package.json +5 -2
package/README.md CHANGED
@@ -1,21 +1,23 @@
1
1
  <div align="center">
2
2
 
3
- # OMSS Core
4
-
5
- <!--
6
- <br />
3
+ <picture>
4
+ <source
5
+ media="(prefers-color-scheme: dark)"
6
+ srcset="https://raw.githubusercontent.com/omss-spec/docs/refs/heads/main/assets/logo-dark.svg"
7
+ />
8
+ <source
9
+ media="(prefers-color-scheme: light)"
10
+ srcset="https://raw.githubusercontent.com/omss-spec/docs/refs/heads/main/assets/logo-light.svg"
11
+ />
7
12
  <img
8
- src="https://raw.githubusercontent.com/omss-spec/graphics/HEAD/omss-landscape-outlined.svg"
13
+ src="https://raw.githubusercontent.com/omss-spec/docs/refs/heads/main/assets/logo-light.svg"
9
14
  width="500"
10
15
  height="auto"
11
16
  alt="OMSS Core"
12
17
  />
13
- <br /><br />
14
- -->
18
+ </picture>
15
19
 
16
- </div>
17
-
18
- <div align="center">
20
+ # Core
19
21
 
20
22
  [![CI](https://github.com/omss-spec/core/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/omss-spec/core/actions/workflows/ci.yml)
21
23
  [![npm version](https://img.shields.io/npm/v/@omss/core.svg?style=flat)](https://www.npmjs.com/package/@omss/core)
@@ -89,13 +91,13 @@ Do you want to know more? Check out the [documentation](https://omss.mintlify.si
89
91
 
90
92
  ## Features
91
93
 
92
- - **Modular by design** the core ships with almost no functionality. Everything is a plugin.
93
- - **OMSS Lifecycle** - use hooks to get notified of OMSS lifecycle events.
94
- - **Fully typed** built in TypeScript with full type exports for **Everything** (no `any` used!)
94
+ - **Modular by design**: The core ships with almost no functionality. Everything is a plugin.
95
+ - **OMSS Lifecycle**: Use hooks to get notified of OMSS lifecycle events.
96
+ - **Fully typed**: Built in TypeScript with full type exports for **Everything** (no `any` used!)
95
97
  - **Extensible**: OMSS Core is fully extensible via its hooks, plugins, and decorators.
96
- - **Middleware support** certain services expose middleware chains that plugins can extend (e.g., caching layers).
97
- - **Developer friendly**: the framework is built to be very expressive and help developers in their daily use without sacrificing performance.
98
- - **Standards-compliant** built with the [OMSS Specification](https://github.com/omss-spec/omss-spec) in mind.
98
+ - **Middleware support**: Certain services expose middleware chains that plugins can extend (e.g., caching layers).
99
+ - **Developer friendly**: The framework is built to be very expressive and help developers in their daily use without sacrificing performance.
100
+ - **Standards-compliant**: Built with the [OMSS Specification](https://github.com/omss-spec/omss-spec) in mind.
99
101
 
100
102
 
101
103
  ## Documentation _(coming soon)_
package/SECURITY.md ADDED
@@ -0,0 +1,39 @@
1
+ # Security Policy
2
+
3
+ ## Supported Versions
4
+
5
+ Only the latest version of the OMSS specification is supported.
6
+
7
+ Once the project reaches a stable release, a proper Long Term Support (LTS) matrix will be published here.
8
+
9
+ ## Reporting a Vulnerability
10
+
11
+ The OMSS team takes security seriously. We appreciate your effort to responsibly disclose vulnerabilities.
12
+
13
+ **Please do NOT open a public GitHub issue for security vulnerabilities.**
14
+
15
+ To report a vulnerability, please use one of the following methods:
16
+
17
+ - **GitHub Security Advisories:** [Report a vulnerability privately](https://github.com/omss-spec/core/security/advisories/new) via GitHub's private reporting feature.
18
+
19
+ ### What to include
20
+
21
+ Please include as much of the following information as possible:
22
+
23
+ - Type of vulnerability (e.g., injection, privilege escalation, information disclosure)
24
+ - Full paths of the affected source file(s)
25
+ - Location of the affected code (tag/branch/commit or direct URL)
26
+ - Any special configuration required to reproduce the issue
27
+ - Step-by-step instructions to reproduce the issue
28
+ - Proof-of-concept or exploit code (if possible)
29
+ - Impact of the vulnerability and how an attacker might exploit it
30
+
31
+ ### Response timeline
32
+
33
+ We will acknowledge receipt of your report within **72 hours** and aim to provide an initial assessment within **10 business days**.
34
+
35
+ We will keep you informed of our progress and notify you when a fix is released. We kindly ask that you refrain from disclosing the vulnerability publicly until a fix has been released.
36
+
37
+ ## Security Acknowledgements
38
+
39
+ We thank all security researchers who have responsibly disclosed vulnerabilities to us. Acknowledged contributors will be listed here upon their consent.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@omss/core",
3
- "version": "0.0.2-beta.2",
3
+ "version": "0.0.2-beta.3",
4
4
  "description": "Official TypeScript runtime and plugin orchestrator to create all kinds of OMSS based services!",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",
@@ -19,7 +19,10 @@
19
19
  }
20
20
  },
21
21
  "files": [
22
- "dist"
22
+ "dist",
23
+ "README.md",
24
+ "SECURITY.md",
25
+ "LICENSE"
23
26
  ],
24
27
  "scripts": {
25
28
  "build": "tsdown",