@nowarajs/totp 1.1.2 → 1.1.3

package/CHANGELOG.md

@@ -1,4 +1,27 @@
 
+## v1.1.3
+
+[compare changes](https://github.com/NowaraJS/totp/compare/v1.1.2...v1.1.3)
+
+### 📖 Documentation
+
+- **📖:** [Add Contributor Covenant Code of Conduct] ([ef8a067](https://github.com/NowaraJS/totp/commit/ef8a067))
+- **📖:** [Add contributing guidelines to the project] ([933b053](https://github.com/NowaraJS/totp/commit/933b053))
+- **📖:** [Add SECURITY.md for vulnerability reporting and supported versions] ([6d888c1](https://github.com/NowaraJS/totp/commit/6d888c1))
+
+### 📦 Build
+
+- **📦:** [Update dependencies and author information in package.json] ([c3eb931](https://github.com/NowaraJS/totp/commit/c3eb931))
+
+### 🦉 Chore
+
+- **🦉:** [Update contact email in issue template] Updated the contact email in the issue template from komiriko@pm.me to nowarajs@pm.me to reflect the correct address for project inquiries. ([b8cc348](https://github.com/NowaraJS/totp/commit/b8cc348))
+- **🦉:** [rename MIT License file with explicit .md] ([cc0cdc8](https://github.com/NowaraJS/totp/commit/cc0cdc8))
+
+### ❤️ Contributors
+
+- Komiroko <komiriko@pm.me>
+
 ## v1.1.2
 
 [compare changes](https://github.com/NowaraJS/totp/compare/v1.1.1...v1.1.2)

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,92 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, please email us at [nowarajs@pm.me](mailto:nowarajs@pm.me).
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+****
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

package/CONTRIBUTING.md

@@ -0,0 +1,173 @@
+# Contributing to Package Template
+
+First off, thanks for taking the time to contribute! ❤️
+
+All types of contributions are encouraged and valued. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions! 🎉
+
+> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
+> - ⭐ Star the project
+> - 🐦 Tweet about it
+> - 📖 Refer this project in your project's readme
+> - 💬 Mention the project at local meetups and tell your friends/colleagues
+
+Please note we have a [Code of Conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Table of Contents
+
+- [I Have a Question](#i-have-a-question)
+- [I Want To Contribute](#i-want-to-contribute)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+  - [Your First Code Contribution](#your-first-code-contribution)
+  - [Improving The Documentation](#improving-the-documentation)
+- [Development Setup](#development-setup)
+- [Style Guidelines](#style-guidelines)
+- [Commit Messages](#commit-messages)
+
+## I Have a Question
+
+> If you want to ask a question, we assume that you have read the available [documentation](./README.md).
+
+Before asking a question, please:
+- Search for existing [issues](https://github.com/NowaraJS/totp/issues) that might help you
+- Check if someone already asked the same question
+
+**How to ask:**
+- [Create a new help & question issue](https://github.com/NowaraJS/totp/issues/new/choose) using our template
+- Or send an email to [nowarajs@pm.me](mailto:nowarajs@pm.me) for quick questions
+
+We'll do our best to help you as soon as possible! 💬
+
+## I Want To Contribute
+
+> ### Legal Notice
+> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
+
+### Reporting Bugs
+
+Found a bug? We'd love to hear about it! 🐞
+
+**Before submitting:**
+- Make sure you're using the latest version
+- Check if the bug has already been reported in our [issues](https://github.com/NowaraJS/totp/issues?q=label%3Abug)
+
+**How to report:**
+Simply [create a new bug report](https://github.com/NowaraJS/totp/issues/new/choose) using our bug report template. The template will guide you through providing all the necessary information we need to investigate and fix the issue quickly.
+
+### Suggesting Enhancements
+
+Have an idea to make the project better? We'd love to hear it! ✨
+
+**Before submitting:**
+- Make sure you're using the latest version
+- Check the [documentation](./README.md) to see if the feature already exists
+- Search [existing enhancement requests](https://github.com/NowaraJS/totp/issues?q=label%3Aenhancement) to avoid duplicates
+
+**How to suggest:**
+[Create a new feature request](https://github.com/NowaraJS/totp/issues/new/choose) using our feature request template. It will help you structure your idea and provide all the context we need to evaluate and potentially implement it.
+
+### Your First Code Contribution
+
+Unsure where to begin contributing? You can start by looking through these `good-first-issue` and `help-wanted` issues:
+
+- [Good first issues](https://github.com/NowaraJS/totp/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - issues which should only require a few lines of code, and a test or two.
+- [Help wanted issues](https://github.com/NowaraJS/totp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) - issues which should be a bit more involved than `good first issue` issues.
+
+### Improving The Documentation
+
+Documentation improvements are always welcome! Whether it's fixing typos, clarifying existing content, or adding new sections, your contributions help make the project more accessible to everyone.
+
+## Development Setup
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/NowaraJS/totp.git
+   cd template-package-npm
+   ```
+
+3. **Install dependencies**:
+   ```bash
+   bun install
+   ```
+
+4. **Create a new branch** for your feature/fix:
+   ```bash
+   git checkout -b feature/your-feature-name
+   # or
+   git checkout -b fix/your-fix-name
+   ```
+
+5. **Make your changes** and ensure they follow our style guidelines
+
+6. **Run the tests** to make sure everything works:
+   ```bash
+   bun run test
+   ```
+
+7. **Run the linter** and fix any issues:
+   ```bash
+   bun run lint
+   # Auto-fix issues with:
+   bun run fix-lint
+   ```
+
+8. **Build the project** to ensure it compiles correctly:
+   ```bash
+   bun run build
+   ```
+
+9. **Commit your changes** following our commit message convention
+
+10. **Push to your fork** and create a pull request
+
+## Style Guidelines
+
+We follow strict TypeScript and coding conventions. Please review our [Copilot Instructions](./.github/copilot-instructions.md) for detailed guidelines, including:
+
+- TypeScript best practices
+- Naming conventions
+- Documentation standards
+- Testing patterns
+- Code organization
+
+### Before Each Commit
+
+- ✅ Run `bun run lint` and fix all errors and warnings
+- ✅ Run relevant unit or integration tests
+- ✅ Update documentation if public APIs or complex logic change
+
+## Commit Messages
+
+We use the Conventional Commits specification with emojis. Format your commits like this:
+
+```
+<type>(<emoji>): [summary up to 72 chars]
+
+[Optional longer description]
+```
+
+**Types:**
+- `feat 🚀` – New features
+- `fix 🔧` – Bug fixes
+- `perf ⚡` – Performance improvements
+- `refactor 🧹` – Refactoring
+- `build 📦` – Build tools / dependency changes
+- `types 🌊` – Type definitions
+- `chore 🦉` – Maintenance, non-code/test changes
+- `docs 📖` – Documentation changes
+- `test 🧪` – Test code updates
+- `style 🎨` – Style/formatting only
+- `ci 🤖` – CI/CD configuration
+
+**Example:**
+```
+feat(🚀): add advanced repository filtering operators
+
+Added $eq, $like, $between filtering operators to repository pattern
+for advanced querying and filtering of database records.
+```
+
+---
+
+Thank you for contributing! 🎉

package/{LICENSE → LICENSE.md}

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 [Project Name]
+Copyright (c) 2025 NowaraJS
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/SECURITY.md

@@ -0,0 +1,15 @@
+# Security Policy
+
+## Supported Versions
+
+The following major versions are currently supported with security updates.
+
+| Version                                                              | End-of-life |
+| -------------------------------------------------------------------- | ----------- |
+| [v1.x](https://github.com/NowaraJS/totp/tree/v1.x)        | TBD         |
+
+End-of-life for the current release will be determined prior to the release of its successor.
+
+## Reporting a Vulnerability
+
+You should report vulnerabilities using the [Github UI](https://github.com/NowaraJS/totp/security/advisories/new) or via email nowarajs@pm.me

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@nowarajs/totp",
-	"version": "1.1.2",
-	"author": "Komiriko",
+	"version": "1.1.3",
+	"author": "NowaraJS",
 	"description": "A comprehensive Time-based One-Time Password (TOTP) and HMAC-based One-Time Password (HOTP)",
 	"type": "module",
 	"license": "MIT",
@@ -22,12 +22,12 @@
 		"test": "bun test --coverage"
 	},
 	"devDependencies": {
-		"@eslint/js": "^9.33.0",
+		"@eslint/js": "^9.34.0",
 		"@stylistic/eslint-plugin": "^5.2.3",
 		"@types/bun": "^1.2.20",
-		"eslint": "^9.33.0",
+		"eslint": "^9.34.0",
 		"globals": "^16.3.0",
-		"typescript-eslint": "^8.39.1",
+		"typescript-eslint": "^8.40.0",
 		"typescript": "^5.9.2"
 	},
 	"exports": {
@@ -89,6 +89,10 @@
 		}
 	},
 	"peerDependencies": {
-		"@nowarajs/error": "^1.1.6"
+		"@nowarajs/error": "^1.1.7"
+	},
+	"repository": {
+		"type": "git",
+		"url": "https://github.com/NowaraJS/totp.git"
 	}
-}
+}