Implement security features in OpenAPI

- Added support for various security schemes including API Key, HTTP Authentication, OAuth 2.0, OpenID Connect, and Mutual TLS.
- Introduced global security requirements that can be applied to all endpoints.
- Enhanced EndpointBuilder to allow setting security requirements at both global and operation levels.
- Created comprehensive tests for security features, including integration tests for complete API scenarios.
- Updated documentation to include detailed explanations of security mechanisms and best practices.

Author: GroophyLifefor

.github/workflows/publish.yml

@@ -16,4 +16,4 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Publish package
-        run: npx jsr publish
+        run: npx jsr publish

deno.json

@@ -1,4 +1,6 @@
 {
+  "name": "@murat/openapi",
+  "exports": "./mod.ts",
   "tasks": {
     "lint": "deno lint",
     "test": "deno test --allow-all",

docs/README.md

@@ -1,29 +1,34 @@
 # OpenAPI Documentation
 
-Welcome to the documentation for the OpenAPI library. This package provides a developer-friendly way to define OpenAPI specifications for your APIs.
+Welcome to the documentation for the OpenAPI library. This package provides a
+developer-friendly way to define OpenAPI specifications for your APIs.
 
 ## Table of Contents
 
 - [Getting Started](./getting-started.md)
 - [EndpointBuilder](./endpoint-builder.md)
 - [OpenAPI Schema](./openapi-schema.md)
+- [Security](./security.md)
+- [Components](./components.md)
 - [Examples](./examples.md)
 
 ## Overview
 
-The OpenAPI library helps you define your API specifications in a structured way following the OpenAPI 3.1 standard. It provides:
+The OpenAPI library helps you define your API specifications in a structured way
+following the OpenAPI 3.1 standard. It provides:
 
 - A fluent API for creating endpoints and their documentation
 - Type-safe schema definitions for request and response objects
 - Tools for serialization to JSON and YAML formats
 - Validation rule handling and documentation
+- Comprehensive security scheme definitions and requirements
 
 ## Basic Usage
 
 Here's a basic example of creating an OpenAPI document:
 
 ```typescript
-import { OpenAPI, EndpointBuilder } from "@murat/openapi";
+import { EndpointBuilder, OpenAPI } from "@murat/openapi";
 
 // Create a new OpenAPI document
 const api = new OpenAPI({
@@ -56,4 +61,5 @@ const jsonString = api.getJSONString();
 const yamlString = api.getYAMLString();
 ```
 
-For more detailed instructions, check out the [Getting Started](./getting-started.md) guide.
+For more detailed instructions, check out the
+[Getting Started](./getting-started.md) guide.

docs/components.md

@@ -1,13 +1,15 @@
 # OpenAPI Components
 
-Components are a powerful feature in OpenAPI 3.1 that allow you to define reusable objects in your API specification. The Components Object holds various schemas that can be referenced throughout the specification.
+Components are a powerful feature in OpenAPI 3.1 that allow you to define
+reusable objects in your API specification. The Components Object holds various
+schemas that can be referenced throughout the specification.
 
 ## Available Component Types
 
 Yelix OpenAPI supports all component types from the OpenAPI 3.1 specification:
 
 - **Schemas**: Reusable schema definitions
-- **Responses**: Reusable response objects  
+- **Responses**: Reusable response objects
 - **Parameters**: Reusable parameter objects
 - **Examples**: Reusable examples
 - **RequestBodies**: Reusable request body objects
@@ -19,16 +21,17 @@ Yelix OpenAPI supports all component types from the OpenAPI 3.1 specification:
 
 ## Adding Components
 
-All component methods return a reference object that can be used in other parts of your API specification.
+All component methods return a reference object that can be used in other parts
+of your API specification.
 
 ### Adding Schemas
 
 ```typescript
-import { OpenAPI } from "yelix/openapi";
+import { OpenAPI } from "jsr:@murat/openapi";
 
 const openapi = new OpenAPI({
   title: "My API",
-  version: "1.0.0"
+  version: "1.0.0",
 });
 
 // Define a reusable schema
@@ -37,9 +40,9 @@ const userSchemaRef = openapi.addSchema("User", {
   properties: {
     id: { type: "integer" },
     name: { type: "string" },
-    email: { type: "string", format: "email" }
+    email: { type: "string", format: "email" },
   },
-  required: ["id", "name", "email"]
+  required: ["id", "name", "email"],
 });
 
 // Now you can reference this schema in your endpoints
@@ -59,12 +62,12 @@ const errorResponseRef = openapi.addResponse("Error", {
         type: "object",
         properties: {
           code: { type: "integer" },
-          message: { type: "string" }
+          message: { type: "string" },
         },
-        required: ["code", "message"]
-      }
-    }
-  }
+        required: ["code", "message"],
+      },
+    },
+  },
 });
 ```
 
@@ -81,8 +84,8 @@ const limitParamRef = openapi.addParameter("limit", {
     type: "integer",
     minimum: 1,
     maximum: 100,
-    default: 20
-  }
+    default: 20,
+  },
 });
 ```
 
@@ -94,7 +97,7 @@ const apiKeyRef = openapi.addSecurityScheme("ApiKey", {
   type: "apiKey",
   name: "X-API-KEY",
   in: "header",
-  description: "API key authentication"
+  description: "API key authentication",
 });
 
 // Define OAuth2 security scheme
@@ -106,19 +109,20 @@ const oauth2Ref = openapi.addSecurityScheme("OAuth2", {
       tokenUrl: "https://example.com/oauth/token",
       scopes: {
         "read:items": "Read items",
-        "write:items": "Write items"
-      }
-    }
-  }
+        "write:items": "Write items",
+      },
+    },
+  },
 });
 ```
 
 ## Using Components with EndpointBuilder
 
-You can use the returned reference objects directly in your operations with EndpointBuilder:
+You can use the returned reference objects directly in your operations with
+EndpointBuilder:
 
 ```typescript
-import { EndpointBuilder } from "yelix/openapi";
+import { EndpointBuilder } from "jsr:@murat/openapi";
 
 // Create an endpoint builder
 const getUserEndpoint = new EndpointBuilder()
@@ -131,16 +135,16 @@ const getUserEndpoint = new EndpointBuilder()
     in: "path",
     required: true,
     schema: {
-      type: "integer"
-    }
+      type: "integer",
+    },
   })
   .addResponse("200", {
     description: "User found",
     content: {
       "application/json": {
-        schema: userSchemaRef // Using the reference from addSchema
-      }
-    }
+        schema: userSchemaRef, // Using the reference from addSchema
+      },
+    },
   })
   .addResponse("404", errorResponseRef); // Using the reference from addResponse
 
@@ -158,7 +162,12 @@ console.log(userSchema);
 
 ## Best Practices
 
-1. **Use Components for Common Objects**: Define schemas, responses, and parameters that are used in multiple endpoints as components.
-2. **Consistent Naming**: Use a consistent naming convention for your components.
-3. **Schema Reuse**: Break down complex schemas into smaller, reusable components.
+1. **Use Components for Common Objects**: Define schemas, responses, and
+   parameters that are used in multiple endpoints as components.
+2. **Consistent Naming**: Use a consistent naming convention for your
+   components.
+3. **Schema Reuse**: Break down complex schemas into smaller, reusable
+   components.
+
+```
 ```