Add documentation, policies, and file module restructure

Introduced CODE_OF_CONDUCT.md, CONTRIBUTING.md, and SECURITY.md for project governance. Updated README with installation, usage, and contribution details. Refactored file-related utilities and tests into a dedicated 'file' module, updated CLI import, and improved documentation structure and assets. Enhanced workflow to only release if src/bin changes, and added scripts/gen-indexes.js for index generation.

Author: teneplaysofficial

.github/workflows/weekly-release.yml

@@ -17,7 +17,7 @@ jobs:
       - name: Check for commits in last 7 days
         id: check
         run: |
-          if git log --since="7 days ago" --oneline | grep .; then
+          if git log --since="7 days ago" --oneline -- src/ bin/ | grep .; then
             echo "has_commits=true" >> $GITHUB_OUTPUT
           else
             echo "has_commits=false" >> $GITHUB_OUTPUT

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We, as contributors, maintainers, and members of the community, pledge to foster an open, welcoming, diverse, inclusive, and harassment-free environment for everyone.
+We are committed to ensuring a positive experience for all participants, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contribute to a positive and respectful environment include:
+
+- Using inclusive and welcoming language
+- Showing respect for differing viewpoints and experiences
+- Offering and receiving constructive feedback with courtesy
+- Taking responsibility for mistakes and learning from them
+- Showing empathy toward others in the community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery
+- Trolling, insults, or derogatory comments
+- Personal or political attacks
+- Public or private harassment
+- Publishing others’ private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for:
+
+- Clarifying the standards of acceptable behavior
+- Monitoring community spaces and interactions
+- Taking appropriate and fair corrective action in response to any behavior deemed inappropriate, threatening, offensive, or harmful
+
+They have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned with this Code of Conduct, and to ban temporarily or permanently any contributor for behavior they deem inappropriate.
+
+## Scope
+
+This Code of Conduct applies within all project spaces such as GitHub repositories, issue trackers, pull requests, and communication channels as well as in public spaces when an individual is representing the project or its community.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior can be reported to the project team at:
+
+**Email:** [tenegamesbusiness@gmail.com](mailto:tenegamesbusiness@gmail.com)
+
+All reports will be reviewed and investigated promptly and fairly. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.

CONTRIBUTING.md

@@ -0,0 +1,124 @@
+# Contributing to JS Utils Kit
+
+Thank you for your interest in contributing to **JS Utils Kit**. Whether you're fixing bugs, proposing new utilities, refining documentation, or improving tests, your contributions are valuable and appreciated.
+
+## Requirements
+
+Before getting started, ensure you have the following installed:
+
+- Node.js
+- Yarn
+- Git
+- TypeScript (used during development)
+
+## Quick Start
+
+1. **Fork the repository** on GitHub.
+
+2. **Clone your fork:**
+
+   ```sh
+   git clone https://github.com/your-username/js-utils-kit.git
+   cd js-utils-kit
+   ```
+
+3. **Install dependencies:**
+
+   ```sh
+   yarn install
+   ```
+
+4. **Run tests:**
+
+   ```sh
+   yarn test
+   ```
+
+## Project Structure
+
+| Directory  | Purpose                                |
+| ---------- | -------------------------------------- |
+| `src/`     | Source code organized by category      |
+| `bin/`     | CLI entry points                       |
+| `tests/`   | Unit tests using Jest                  |
+| `scripts/` | Development tools (e.g. index builder) |
+| `docs/`    | Generated TypeDoc documentation        |
+
+## Scripts
+
+| Command            | Description                                       |
+| ------------------ | ------------------------------------------------- |
+| `yarn test`        | Run all Jest tests                                |
+| `yarn gen:indexes` | Generate export indexes for all categories        |
+| `yarn build`       | Compile project to CJS, ESM, and type files       |
+| `yarn docs`        | Generate TypeScript documentation via TypeDoc     |
+| `prebuild`         | Automatically runs `gen:indexes` before build     |
+| `postbuild`        | Automatically generates documentation after build |
+
+## Development Workflow
+
+1. **Create a new branch:**
+
+   ```sh
+   git checkout -b feat/your-feature-name
+   ```
+
+2. **Make changes and commit with a clear message:**
+
+   ```sh
+   git commit -m "feat: add clamp utility"
+   ```
+
+3. **Test and build before opening a PR:**
+
+   ```sh
+   yarn test
+   yarn build
+   ```
+
+4. **Push and open a Pull Request on GitHub.**
+
+## Commit Guidelines
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/) for commit messages:
+
+- `feat:` for new features
+- `fix:` for bug fixes
+- `docs:` for documentation changes
+- `refactor:` for code refactoring (no feature or fix)
+- `test:` for adding or updating tests
+- `chore:` for tooling, CI, or build changes
+
+## Testing
+
+All tests are located in the `tests/` directory and use [Jest](https://jestjs.io).
+
+To run the test suite:
+
+```sh
+yarn test
+```
+
+Ensure new utilities are covered with appropriate test cases.
+
+## CLI Usage
+
+The CLI entry point is in `bin/index.ts`, powered by [Commander](https://github.com/tj/commander.js).
+
+To test it locally:
+
+```sh
+node dist/cli/index.js --help
+```
+
+## Pull Request Checklist
+
+Before opening a pull request, make sure:
+
+- [ ] The change has a clear purpose
+- [ ] Related tests are added or updated
+- [ ] The utility is compatible with both ESM and CJS
+- [ ] The utility is properly exported in `index.ts`
+- [ ] There are no unintended breaking changes
+
+If you have questions or need clarification, feel free to open an issue or start a discussion. Thank you for helping improve JS Utils Kit.

README.md

@@ -1,3 +1,54 @@
 # JS Utils Kit
 
-A compact library of essential JavaScript utility functions—such as array operations, object helpers, Promise utilities, and type checks. Designed to be lightweight, dependable, and effortlessly integrated into JS or TS projects, it has minimal bundle impact and works seamlessly with modern bundlers.
+[![npm version](https://img.shields.io/npm/v/js-utils-kit.svg)](https://www.npmjs.com/package/js-utils-kit)
+[![License](https://img.shields.io/github/license/TenEplaysOfficial/js-utils-kit.svg)](LICENSE)
+
+**JS Utils Kit** is a compact and reliable library of essential JavaScript utility functions. It includes helpers for arrays, objects, numbers, promises, type checking, and more. Designed for performance and modularity, it integrates easily into JavaScript and TypeScript projects with minimal impact on bundle size.
+
+> Lightweight. Dependable. Modular.
+
+## Installation
+
+```sh
+yarn add js-utils-kit
+# or
+npm install js-utils-kit
+```
+
+## Usage
+
+```ts
+import * as kit from 'js-utils-kit';
+
+// Number utilities
+kit.number.clamp(10, 0, 100);
+
+// Root-level utilities
+kit.isNode();
+```
+
+## Features
+
+- Organized by category (e.g., `number`, `string`, `file`, etc.)
+- Fully typed with TypeScript
+- Thoroughly tested with Jest
+- Tree-shakable and supports both ESM and CJS
+- CLI-ready tools for file and system operations
+
+## Documentation
+
+Full documentation available at [GitHub Pages](https://teneplaysofficial.github.io/js-utils-kit/)
+
+## Requirements
+
+- Node.js
+- Yarn
+- TypeScript (for development)
+
+## Contributing
+
+Contributions are welcome. Please refer to [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+
+## License
+
+[MIT](LICENSE)

SECURITY.md

@@ -0,0 +1,42 @@
+# Security Policy
+
+## Supported Versions
+
+Only the latest **major** release of `js-utils-kit` is actively maintained and supported. Previous versions may not receive security patches unless otherwise stated.
+
+| Version | Supported |
+| ------- | --------- |
+| 1.x     | Yes       |
+| <1.0.0  | No        |
+
+## Reporting a Vulnerability
+
+If you discover a potential security vulnerability in this project:
+
+1. **Do not open a public GitHub issue.**
+
+2. Contact the maintainers directly via email:
+
+   **Email:** [tenegamesbusiness@gmail.com](mailto:tenegamesbusiness@gmail.com)
+
+3. Include the following details in your report:
+   - Affected version(s)
+   - Steps to reproduce or a proof-of-concept
+   - Description of the potential impact
+   - Suggested remediation or workaround (if known)
+
+## Disclosure Policy
+
+We aim to respond to all vulnerability reports within **72 hours**. If the issue is confirmed, appropriate actions may include:
+
+- Releasing a patch or hotfix
+- Providing recommended mitigations or workarounds
+- Publishing a security advisory through GitHub
+
+You may be credited for responsible disclosure, unless you request to remain anonymous.
+
+## Responsible Disclosure
+
+We follow responsible disclosure practices. Please refrain from sharing security vulnerabilities publicly until they have been investigated, validated, and addressed through an official fix or advisory.
+
+Thank you for helping make `js-utils-kit` more secure.

bin/index.ts

@@ -1,7 +1,7 @@
 import fs from 'fs';
 import ora from 'ora';
 import { Command } from 'commander';
-import { createArchive } from '../src';
+import { createArchive } from '../src/file';
 
 const pkg = JSON.parse(fs.readFileSync('./package.json', 'utf8'));
 

docs/assets/highlight.css

@@ -1,18 +1,22 @@
 :root {
-    --light-hl-0: #000000;
-    --dark-hl-0: #D4D4D4;
-    --light-hl-1: #001080;
-    --dark-hl-1: #9CDCFE;
+    --light-hl-0: #795E26;
+    --dark-hl-0: #DCDCAA;
+    --light-hl-1: #000000;
+    --dark-hl-1: #D4D4D4;
     --light-hl-2: #A31515;
     --dark-hl-2: #CE9178;
-    --light-hl-3: #000000;
-    --dark-hl-3: #C8C8C8;
+    --light-hl-3: #008000;
+    --dark-hl-3: #6A9955;
     --light-hl-4: #AF00DB;
     --dark-hl-4: #C586C0;
-    --light-hl-5: #795E26;
-    --dark-hl-5: #DCDCAA;
-    --light-hl-6: #0000FF;
-    --dark-hl-6: #569CD6;
+    --light-hl-5: #0000FF;
+    --dark-hl-5: #569CD6;
+    --light-hl-6: #001080;
+    --dark-hl-6: #9CDCFE;
+    --light-hl-7: #098658;
+    --dark-hl-7: #B5CEA8;
+    --light-hl-8: #000000;
+    --dark-hl-8: #C8C8C8;
     --light-code-background: #FFFFFF;
     --dark-code-background: #1E1E1E;
 }
@@ -25,6 +29,8 @@
     --hl-4: var(--light-hl-4);
     --hl-5: var(--light-hl-5);
     --hl-6: var(--light-hl-6);
+    --hl-7: var(--light-hl-7);
+    --hl-8: var(--light-hl-8);
     --code-background: var(--light-code-background);
 } }
 
@@ -36,6 +42,8 @@
     --hl-4: var(--dark-hl-4);
     --hl-5: var(--dark-hl-5);
     --hl-6: var(--dark-hl-6);
+    --hl-7: var(--dark-hl-7);
+    --hl-8: var(--dark-hl-8);
     --code-background: var(--dark-code-background);
 } }
 
@@ -47,6 +55,8 @@
     --hl-4: var(--light-hl-4);
     --hl-5: var(--light-hl-5);
     --hl-6: var(--light-hl-6);
+    --hl-7: var(--light-hl-7);
+    --hl-8: var(--light-hl-8);
     --code-background: var(--light-code-background);
 }
 
@@ -58,6 +68,8 @@
     --hl-4: var(--dark-hl-4);
     --hl-5: var(--dark-hl-5);
     --hl-6: var(--dark-hl-6);
+    --hl-7: var(--dark-hl-7);
+    --hl-8: var(--dark-hl-8);
     --code-background: var(--dark-code-background);
 }
 
@@ -68,4 +80,6 @@
 .hl-4 { color: var(--hl-4); }
 .hl-5 { color: var(--hl-5); }
 .hl-6 { color: var(--hl-6); }
+.hl-7 { color: var(--hl-7); }
+.hl-8 { color: var(--hl-8); }
 pre, code { background: var(--code-background); }