Initial commit

.commitlintrc.json

@@ -0,0 +1,36 @@
+{
+	"extends": [
+		"@commitlint/config-angular"
+	],
+	"rules": {
+		"subject-case": [
+			2,
+			"always",
+			[
+				"sentence-case",
+				"start-case",
+				"pascal-case",
+				"upper-case",
+				"lower-case"
+			]
+		],
+		"type-enum": [
+			2,
+			"always",
+			[
+				"build",
+				"chore",
+				"ci",
+				"docs",
+				"feat",
+				"fix",
+				"perf",
+				"refactor",
+				"revert",
+				"style",
+				"test",
+				"sample"
+			]
+		]
+	}
+}

.editorconfig

@@ -0,0 +1,19 @@
+# editorconfig.org
+root = true
+
+[*]
+end_of_line = lf
+indent_style = tab
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_size = 4
+max_line_length = 140
+
+[*.{yaml, yml}]
+indent_style = space
+indent_size = 2
+
+[*.md]
+indent_style = space
+trim_trailing_whitespace = false

.eslintrc

@@ -0,0 +1,29 @@
+{
+	"parser": "@typescript-eslint/parser",
+	"parserOptions": {
+		"project": "tsconfig.json",
+		"sourceType": "module"
+	},
+	"plugins": [
+		"@typescript-eslint/eslint-plugin"
+	],
+	"extends": [
+		"plugin:@typescript-eslint/eslint-recommended",
+		"plugin:@typescript-eslint/recommended",
+		"prettier"
+	],
+	"root": true,
+	"env": {
+		"node": true
+	},
+	"rules": {
+		"@typescript-eslint/interface-name-prefix": "off",
+		"@typescript-eslint/explicit-function-return-type": "off",
+		"@typescript-eslint/no-explicit-any": "off",
+		"@typescript-eslint/explicit-module-boundary-types": "off",
+		"@typescript-eslint/no-unused-vars": "off",
+		"@typescript-eslint/ban-types": "off",
+		"@typescript-eslint/no-empty-interface": "off"
+	}
+}
+

.gitattributes

@@ -0,0 +1,3 @@
+yarn.lock   -diff -merge
+yarn.lock    linguist-generated=true
+* text 		 eol=lf

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @SocketSomeone

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making 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,
+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 to 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. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at socket.someone@gmail.com. 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][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/COMMIT_CONVENTION.md

@@ -0,0 +1,59 @@
+## Git Commit Message Convention
+
+> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
+
+#### TL;DR:
+
+Messages must be matched by the following regex:
+
+```js
+/^(revert: )?(feat|fix|docs|style|refactor|perf|test|workflow|build|ci|chore|types|wip)(\(.+\))?: .{1,72}/;
+```
+
+### Full Message Format
+
+A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
+
+```
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+### Revert
+
+If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
+
+### Type
+
+If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
+
+Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
+
+### Scope
+
+The scope could be anything specifying the place of the commit change. For example `SlashCommand`, `ContextMenu`, `MessageComponents` etc...
+
+### Subject
+
+The subject contains a succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+### Body
+
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
+
+### Footer
+
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.
+
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: [SocketSomeone]

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,12 @@
+**Please describe the changes this PR makes and why it should be merged:**
+
+**Status and versioning classification:**
+
+<!--
+Please move lines that apply to you out of the comment:
+- Code changes have been tested against the Discord API, or there are no code changes
+- I know how to update typings and have done so, or typings don't need updating
+- This PR changes the library's interface (methods or parameters added)
+- This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
+- This PR **only** includes non-code changes, like changes to documentation, README, etc.
+-->

.github/SECURITY.md

@@ -0,0 +1,5 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Please report security issues to `socket.someone@gmail.com`.

.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    rebase-strategy: "auto"
+    directory: "/"
+    schedule:
+      interval: daily
+  - package-ecosystem: npm
+    rebase-strategy: "auto"
+    directory: "/"
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 10
+

.github/husky/.gitignore

@@ -0,0 +1 @@
+_

.github/husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx commitlint --config .commitlintrc.json --edit $HUSKY_GIT_PARAMS

.github/husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx lint-staged

.github/labels.yml

@@ -0,0 +1,46 @@
+- name: 'backlog'
+  color: '7ef7ef'
+- name: 'bug'
+  color: 'd73a4a'
+- name: 'chore'
+  color: 'ffffff'
+- name: 'ci'
+  color: '0075ca'
+- name: 'dependencies'
+  color: '276bd1'
+- name: 'discussion'
+  color: 'b6b1f9'
+- name: 'documentation'
+  color: '0075ca'
+- name: 'duplicate'
+  color: 'cfd3d7'
+- name: 'feature request'
+  color: 'fcf95a'
+- name: 'good first issue'
+  color: '7057ff'
+- name: 'help wanted'
+  color: '008672'
+- name: 'in progress'
+  color: 'ffccd7'
+- name: 'in review'
+  color: 'aed5fc'
+- name: 'invalid'
+  color: 'e4e669'
+- name: 'need repro'
+  color: 'c66037'
+- name: 'performance'
+  color: '80c042'
+- name: 'priority:high'
+  color: 'fc1423'
+- name: 'question'
+  color: 'd876e3'
+- name: 'refactor'
+  color: '1d637f'
+- name: 'regression'
+  color: 'ea8785'
+- name: 'tests'
+  color: 'f06dff'
+- name: 'utility'
+  color: '80c042'
+- name: 'wontfix'
+  color: 'ffffff'

.github/workflows/auto-deprecate.yml

@@ -0,0 +1,27 @@
+name: NPM auto deprecate
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 1 * * *'
+jobs:
+  auto-deprecate:
+    name: NPM auto deprecate
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install Node v18
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: yarn
+          cache-dependency-path: yarn.lock
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+
+      - name: Deprecate versions
+        run: 'npx @favware/npm-deprecate --name "*dev*" --package "nestjs-open-source-template"'
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}