Merge pull request #5 from LynnuxDev/backup-branch

Backup branch

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, 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 and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0.

.github/FUNDING.yml

@@ -0,0 +1,11 @@
+github: Dark-LYNN
+patreon: Dark_Lynn
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with custom url

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[Bug]"
+labels: bug
+assignees: Dark-LYNN
+
+---
+
+## Bug Report
+
+**Describe the Bug:**
+A clear and concise description of what the bug is.
+
+**To Reproduce:**
+Steps to reproduce the behavior:
+
+1. '...' *(optional)*
+2. Command used '....' *\**
+3. what you get '...' *\**
+
+**Expected Behavior:**
+A clear and concise description of what you expected to happen.
+
+**Screenshots:**
+If applicable, add screenshots to help explain your problem.
+
+**Environment:**
+
+- Bot Version: `[e.g., v1.0.0]` *(if enabled)*
+- Your serverID/Name `[e.g., 1153968713276604436]`
+- Your userID/Name: `[e.g., LynnuxDev]`
+
+**Additional Context:**
+Add any other context about the problem here.
+
+**Possible Solution:**
+If you have a suggestion on how to fix the bug or what might be causing it, please let us know.
+
+---
+
+**Note:**
+
+- Before submitting, please make sure that the bot is not currently down.
+- Search for existing issues to avoid duplication.
+- If the bug is related to a specific command or feature, please mention it.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,15 @@
+blank_issues_enabled: false
+contact_links:
+  - name: GitHub Community Support
+    url: https://github.com/LynnuxDev/Akira/discussions
+    about: Please ask and answer questions here.
+  - name: Report a vulnerability
+    url: https://github.com/LynnuxDev/Akira/security/advisories/new
+    about: Please report security vulnerabilities here.
+templates:
+  - name: "Bug report"
+    description: "Create a bug report template"
+    filename: "bug_report.md"
+  - name: "Feature request"
+    description: "Submit a feature request"
+    filename: "feature_request.md"

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: Dark-LYNN
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/SECURITY.md

@@ -0,0 +1,40 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+At LynnuxDev, we take security seriously. If you discover a security vulnerability in Akira, we appreciate your help in disclosing it to us in a responsible manner.
+
+To report a security vulnerability, please email us at [[email protected]](mailto:[email protected]) with the details. We request that you do not publicly disclose the issue until we have had a chance to address it.
+
+## Security Response Process
+
+We strive to respond to security vulnerability reports promptly. Here's what you can expect:
+
+- Once a report is received, we will acknowledge its receipt within 2 business days.
+- Our team will review the report and assess the impact and severity.
+- If necessary, we will work with you to understand the steps to reproduce and validate the vulnerability.
+- Once validated, we will work on developing a fix for the issue.
+- A security release will be issued within 5 to 10 business days to address the vulnerability, and we will coordinate with you on an appropriate disclosure timeline.
+
+## Guidelines for Reporting Security Issues
+
+When reporting a security issue, please provide the following information:
+
+- Your Discord server/username (or other contact information, if applicable).
+- A clear and concise description of the vulnerability.
+- Steps to reproduce the vulnerability.
+- Any additional information that might help us understand and address the issue.
+
+We appreciate your contribution to the security of Akira. Thank you for helping us keep our community safe.
+
+## Responsible Disclosure
+
+We encourage responsible disclosure of security vulnerabilities. We kindly request that you:
+
+- Refrain from disclosing the issue publicly until we have had a chance to address it.
+- Do not exploit the vulnerability for any reason.
+- Provide us with a reasonable amount of time to address and fix the vulnerability before any public disclosure.
+
+Thank you for your understanding and cooperation.
+
+---

.github/custom-properties.json

@@ -0,0 +1,11 @@
+{
+  "botName": "Akira",
+  "primaryLanguage": "TypeScript",
+  "minimumNodeVersion": "22.3.0",
+  "communityStatus": "active",
+  "license": "MIT",
+  "features": {
+    "autoModeration": "beta",
+    "roleplay": "beta"
+  }
+}

.github/dependabot.yml

@@ -0,0 +1,31 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    allow:
+      - dependency-name: "@tryforge/forge.api"
+      - dependency-name: "@tryforge/forgescript"
+      - dependency-name: "@tryforge/forge.db"
+      - dependency-name: "discord.js"
+      - dependency-name: "typescript"
+      - dependency-name: "sqlite3"
+      - dependency-name: "node.js"
+    commit-message:
+      prefix: "npm"
+      prefix-development: "npm dev"
+    labels:
+      - "npm"
+      - "dependencies"
+    pull-request-branch-name:
+      separator: "-"

.github/workflows/read-properties.yml

@@ -0,0 +1,12 @@
+name: Read Custom Properties
+on: push
+jobs:
+  read-properties:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v3
+
+      - name: Read Custom Properties
+        run: |
+          cat .github/custom-properties.json

.gitignore

@@ -8,3 +8,5 @@ TODO.MD
 forge.db
 src/handler/token.ts
 src/handler/encryptionKey.ts
+pnpm-lock.yaml
+files/anime/not-found.json

Errors.md → INFO/Errors.md

@@ -57,6 +57,7 @@ table of content
 | 720    | User doesn't have perms | The user who ran the command doesn't have the right server specific perms. |
 | 721    | User cannot be Author  | The user given cannot be the author. |
 | 722    | Target user blocked    | The user given has blocked someone/anyone from using this command on them. |
+| 723    | User input required    | There must be a user given in the query |
 | 801    | Perms reply            | when the user uses perms reply with wrong input. |
 | 802    | Perms list             | Wrong argument for a.perms list. The argument needs to be a user / role / channel. |
 | 803    | Perms default          | No argument for default. |

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 LynnuxDev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+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:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+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.