feat: add CODEOWNERS and project instructions for GitHub Action

Author: GeekMasher

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# This project is maintained with love by:
+
+- @advanced-security/oss-maintainers

.github/dependabot.yml

@@ -0,0 +1,23 @@
+# 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: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    reviewers:
+      - "advanced-security/oss-maintainers"
+    groups:
+      extractor:
+        dependency-type: "production"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    reviewers:
+      - "advanced-security/oss-maintainers"

.github/instructions/project.instructions.md

@@ -0,0 +1,29 @@
+---
+applyTo: '**/*.rs'
+---
+
+This is a GitHub Action that that allows you to specify a CodeQL extractor to be used in your workflows as an author of an Extractor.
+It is designed to be used in conjunction with the [CodeQL][CodeQL] analysis tool, which is a powerful static analysis tool that can be used to find vulnerabilities in your code.
+
+The project is written in Rust and used the [ghactions](https://crates.io/crates/ghactions) crate to simplify the development of GitHub Actions in Rust.
+The action is built using a Debian based Docker image.
+
+## Guildelins
+
+- Use cargo fmt to format the code.
+- Use cargo clippy to lint the code.
+- Always write documentation for public functions and modules.
+- Write unit tests for all public functions.
+- Use `log::info!`, `log::warn!`, `log::error!` for logging.
+
+## Testing
+
+You can test the Rust code locally using `cargo tests`.
+
+```sh
+cargo test
+```
+
+This will run all the tests in the project and display the results in the terminal.
+Validate the output of the tests to ensure that everything is working as expected.
+If the tests fail, debug the code and fix any issues before proceeding.