bas 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 9d8ff973fc126ff9d0af5adf9200417f302a9a86cc50be3d3ef090a8979a22b1
+  data.tar.gz: 846dfe3cd6d719aa0a7cc17ce2219a0dee54a5d89043a475ec93b4786fd688d2
+SHA512:
+  metadata.gz: 14ea01f630b4a296fa94a352d14bc00111833d2f5b1867861280c5aa32abca445bdc7ec888c83a4a673109aba2c5e3239fdccc48cc7315477a3b579d200b649c
+  data.tar.gz: 3b73cf8b1dc7d931c3cd428141f2a3806c1b90c23bb1c0ac2dc755bf16278b679f42405f4d504b5cfbd6d1f09787d065f34fe3a06cee15ed9d684a93d2249971

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,14 @@
+AllCops:
+  TargetRubyVersion: 2.6
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Metrics/BlockLength:
+  Exclude:
+    - 'spec/**/*_spec.rb'

data/CHANGELOG.md

@@ -0,0 +1,4 @@
+# Changelog
+
+## 0.1.0 (26.03.2024)
+- [Add the BNS gem code](https://github.com/kommitters/bas/issues/1)

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community includes:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing other's private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official 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 to the community leaders responsible for enforcement at [oss@kommit.co](mailto:oss@kommit.co).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributing 🎉
+
+Hi there! We are thrilled that you'd like to contribute to this project. Your help is essential for keeping it great 🙌.
+
+Contributions to this project are [released][contributions-under-repo] to the public under the project's open source license.
+
+Here are a few things you can do that will increase the likelihood of your pull request being accepted:
+- Follow standards for style and code quality.
+- Write tests (if applicable).
+- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
+- Write a [good commit message][commit-msg].
+- All content, comments, pull requests and other contributions must comply with the [code of conduct][coc].
+
+## Getting started
+
+* Make sure you have a [GitHub account][github-signup].
+* Create a GitHub issue for your contribution, assuming one does not already exist.
+  * Choose one of the templates and clearly describe the issue.
+* Fork the repository on GitHub.
+* Try to keep your local repository in a "rebased" state.
+
+## Finding things to work on
+
+Issues marked with [good first issue][good-first-issue] or [help wanted][help-wanted] are usually pretty self-contained and a good place to get started.
+
+If you see any issues that are assigned to a particular person or have the `📍 Work in progress` label, that means
+someone is currently working on that issue this issue in the next week or two.
+
+Of course, feel free to create a new issue if you think something needs to be added or fixed.
+
+## Making changes
+
+* Create a topic branch from where you want to base your work `git checkout -b my-branch-name`.
+  * This is usually the `main` branch.
+  * Please avoid working directly on the `main` branch.
+
+## Submitting changes
+* Push changes to your fork.
+* Submit a pull request.
+
+At this point, you're waiting on us. We like to at least comment on pull requests within three
+business days (typically, one business day). We may suggest some changes, improvements or
+alternatives.
+
+## Resources
+
+- [How to Contribute to Open Source][oss-how-to]
+- [Using Pull Requests][github-help-pr]
+- [GitHub Help][github-help]
+
+## Contact
+
+Get in touch: [oss@kommit.co][mail-to] | [@kommitters_oss][twitter] on Twitter.
+
+
+[twitter]: https://twitter.com/kommitters_oss
+[mail-to]: mailto:oss@kommit.co
+[github-signup]: https://github.com/signup/free
+[github-help]: https://help.github.com
+[github-help-pr]: https://help.github.com/articles/about-pull-requests
+[oss-how-to]: https://opensource.guide/how-to-contribute
+[coc]: https://github.com/kommitters/soroban-did-contract/blob/main/CODE_OF_CONDUCT.md
+[commit-msg]: https://github.com/erlang/otp/wiki/Writing-good-commit-messages
+[good-first-issue]: https://github.com/kommitters/soroban-did-contract/issues?q=is%3Aopen+is%3Aissue+label%3A%22%F0%9F%91%8B+Good+first+issue%22
+[help-wanted]: https://github.com/kommitters/soroban-did-contract/issues?q=is%3Aopen+is%3Aissue+label%3A%22%F0%9F%86%98+Help+wanted%22
+[contributions-under-repo]: https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license

data/Gemfile

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in bas.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "net-imap", "~> 0.4.10"
+gem "net-smtp", "~> 0.4.0.1"
+gem "rspec", "~> 3.0"
+gem "rubocop", "~> 1.21"
+gem "simplecov", require: false, group: :test
+gem "simplecov-lcov", "~> 0.8.0"
+
+gem "vcr"
+gem "webmock"
+
+gem "httparty"
+
+gem "pg", "~> 1.5", ">= 1.5.4"
+
+gem "gmail_xoauth"

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 kommitters Open Source
+
+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.

data/README.md

@@ -0,0 +1,362 @@
+# BAS - Business Automation System
+
+Many organizations and individuals rely on automation across various contexts in their daily operations. With BAS, we aim to provide an open-source platform that empowers users to create customized automation systems tailored to their unique requirements. BAS consists of a series of abstract components designed to facilitate the creation of diverse use cases, regardless of context.
+
+The underlying idea is to develop generic components that can serve a wide range of needs, this approach ensures that all members of the community can leverage the platform's evolving suite of components and use cases to their advantage.
+
+![Gem Version](https://img.shields.io/gem/v/bas?style=for-the-badge)
+![Gem Total Downloads](https://img.shields.io/gem/dt/bas?style=for-the-badge)
+![Build Badge](https://img.shields.io/github/actions/workflow/status/kommitters/bas/ci.yml?branch=project-opensource-config&style=for-the-badge)
+[![Coverage Status](https://img.shields.io/coveralls/github/kommitters/bas?style=for-the-badge)](https://coveralls.io/github/kommitters/bas?branch=main)
+![GitHub License](https://img.shields.io/github/license/kommitters/bas?style=for-the-badge)
+[![OpenSSF Scorecard](https://img.shields.io/ossf-scorecard/github.com/kommitters/bas?label=openssf%20scorecard&style=for-the-badge)](https://api.securityscorecards.dev/projects/github.com/kommitters/bas)
+[![OpenSSF Best Practices](https://img.shields.io/cii/summary/8383?label=openssf%20best%20practices&style=for-the-badge)](https://bestpractices.coreinfrastructure.org/projects/8383)
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+    $ bundle add bas
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    $ gem install bas
+
+## Requirements
+
+* Ruby 2.6.0 or higher
+
+## Building my own use case
+
+The gem provides with basic interfaces, types, and methods to shape your own use cases in an easy way.
+
+There are 7 currently implemented use cases:
+* Birthday notifications - from Notion to Discord
+* Next Week Birthday notifications - from Notion to Discord
+* PTO notifications - from Notion to Discord
+* Next Week PTO notifications - from Notion to Discord
+* PTO notifications - from Postgres to Slack
+* WIP limit exceeded - from Notion to Discord
+* Support email notification - from IMAP to Discord
+
+For this example we'll analyze the birthday notification use case, bringing data from a notion database, and dispatching the
+notifications to a Discord channel.
+
+A *Use Case* object, consists on 4 main components, having it's own responsibility:
+
+### 1. Fetcher - Obtaining the data
+
+Specifically, a fetcher is an object in charged of bringing data from a data source. The gem already provides the base interface
+for building your own fetcher for your specific data source, or rely on already built classes if they match your purpose.
+
+The base interface for a fetcher can be found under the `bas/fetcher/base.rb` class. Since this is a implementation of the `Fetcher::Base`
+for bringing data from a Notion database, it was created on a new namespace for that data source, it can be found under
+`/bas/fetcher/notion/use_case/birthday_today.rb`. It implements specific logic for fetching the data and validating the response.
+
+### 2. Mapper - Shaping it
+
+The **Mapper** responsibility, is to shape the data using custom types from the app domain, bringing it into a
+common structure understandable for other components, specifically the **Formatter**.
+
+Because of the use case, the Mapper implementation for it, relies on specific types for representing a Birthday it self. It can be found
+under `/bas/mapper/notion/birthday_today.rb`
+
+### 3. Formatter - Preparing the message
+
+The **Formatter**, is in charge of preparing the message to be sent in our notification, and give it the right format with the right data.
+The template or 'format' to be used should be included in the use case configurations, which we'll review in a further step. It's
+implementation can be found under `/bas/formatter/birthday.rb`.
+
+### 4. Dispatcher - Sending your notification
+
+Finally, the **Dispatcher** basically, sends or dispatches the formatted message into a destination, since the use case was implemented for
+Discord, it implements specific logic to communicate with a Discord channel using a webhook. The webhook configuration and name for the 'Sender'
+in the channel should be provided with the initial use case configurations. It can be found under `/bas/dispatcher/discord/implementation.rb`
+
+## Examples
+
+In this example, we demonstrate how to instantiate a birthday notification use case and execute it in a basic Ruby project. We'll also cover its deployment in a serverless configuration, specifically using a simple Lambda deployment.
+
+### Preparing the configurations
+
+We'll need some configurations for this specific use case:
+* A **Notion database ID**, from a database with the following structure:
+
+| Complete Name (text) |    BD_this_year (formula)   |         BD (date)        |
+| -------------------- | --------------------------- | ------------------------ |
+|       John Doe       |       January 24, 2024      |      January 24, 2000    |
+|       Jane Doe       |       June 20, 2024         |      June 20, 2000       |
+
+With the following formula for the **BD_this_year** column: `dateAdd(prop("BD"), year(now()) - year(prop("BD")), "years")`
+
+* A Notion secret, which can be obtained, by creating an integration here: `https://developers.notion.com/`, browsing on the **View my integrations** option, and selecting the **New Integration** or **Create new integration** buttons.
+
+* A webhook key, which can be generated directly on discord on the desired channel, following this instructions: `https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks`
+
+* A filter, to determine which data to bring from the database, for this specific case, the filter we used is:
+
+```
+#### file.rb ####
+today = Date.now
+{
+    "filter": {
+      "or": [
+        {
+          "property": "BD_this_year",
+          "date": {
+            "equals": today
+          }
+        }
+      ]
+    },
+    "sorts": []
+}
+```
+
+* A template for the formatter to be used for formatting the payload to dispatch to Discord. For this specific case, the format of the messages should be:
+
+`"NAME, Wishing you a very happy birthday! Enjoy your special day! :birthday: :gift:"`
+
+### Instantiating the Use Case
+
+To instantiate the use case, the `UseCases` module should provide a method for this purpose, for this specific case, the `notify_birthday_from_notion_to_discord`
+is the desired one.
+
+**Normal ruby code**
+```
+filter = {
+    "filter": {
+      "or": [
+        {
+          "property": "BD_this_year",
+          "date": {
+            "equals": today
+          }
+        }
+      ]
+    },
+    "sorts": []
+}
+
+options = {
+    fetch_options: {
+      base_url: "https://api.notion.com",
+      database_id: NOTION_DATABASE_ID,
+      secret: NOTION_API_INTEGRATION_SECRET,
+      filter: filter
+    },
+    dispatch_options: {
+      webhook: "https://discord.com/api/webhooks/1199213527672565760/KmpoIzBet9xYG16oFh8W1RWHbpIqT7UtTBRrhfLcvWZdNiVZCTM-gpil2Qoy4eYEgpdf",
+      name: "Birthday Bot"
+    }
+}
+
+use_case = UseCases.notify_birthday_from_notion_to_discord(options)
+
+use_case.perform
+
+```
+
+### Serverless
+We'll explain how to configure and deploy a use case with serverless, this example will cover the PTO's notifications use case.
+
+#### Configuring environment variables
+Create the environment variables configuration file.
+
+```bash
+cp env.yml.example env.yml
+```
+
+And put the following env variables
+```
+dev:
+  NOTION_DATABASE_ID: NOTION_DATABASE_ID
+  NOTION_SECRET: NOTION_SECRET
+  DISCORD_WEBHOOK: DISCORD_WEBHOOK
+  DISCORD_BOT_NAME: DISCORD_BOT_NAME
+prod:
+  NOTION_DATABASE_ID: NOTION_DATABASE_ID
+  NOTION_SECRET: NOTION_SECRET
+  DISCORD_WEBHOOK: DISCORD_WEBHOOK
+  DISCORD_BOT_NAME: DISCORD_BOT_NAME
+
+```
+
+The variables should be defined either in the custom settings section within the `serverless.yml` file to ensure accessibility by all lambdas, or in the environment configuration option for each lambda respectively. For example:
+
+```bash
+# Accessible by all the lambdas
+custom:
+  settings:
+      api:
+        NOTION_DATABASE_ID: ${file(./env.yml):${env:STAGE}.NOTION_DATABASE_ID}
+        NOTION_SECRET: ${file(./env.yml):${env:STAGE}.NOTION_SECRET}}
+
+# Accessible by the lambda
+functions:
+  lambdaName:
+    environment:
+      NOTION_DATABASE_ID: ${file(./env.yml):${env:STAGE}.NOTION_DATABASE_ID}
+      NOTION_SECRET: ${file(./env.yml):${env:STAGE}.NOTION_SECRET}}
+```
+
+#### Schedule
+the schedule is configured using an environment variable containing the cron configuration. For example:
+```bash
+# env.yml file
+SCHEDULER: cron(0 13 ? * MON-FRI *)
+
+# serverless.yml
+functions:
+  lambdaName:
+    events:
+      - schedule:
+        rate: ${file(./env.yml):${env:STAGE}.SCHEDULER}
+```
+
+To learn how to modify the cron configuration follow this guide: [Schedule expressions using rate or cron](https://docs.aws.amazon.com/lambda/latest/dg/services-cloudwatchevents-expressions.html)
+
+#### Building your lambda
+On your serverless configuration, create your lambda function, on your serverless `/src` folder.
+
+```ruby
+# frozen_string_literal: true
+
+require 'bas'
+
+# Initialize the environment variables
+NOTION_BASE_URL = 'https://api.notion.com'
+NOTION_DATABASE_ID = ENV.fetch('PTO_NOTION_DATABASE_ID')
+NOTION_SECRET = ENV.fetch('PTO_NOTION_SECRET')
+DISCORD_WEBHOOK = ENV.fetch('PTO_DISCORD_WEBHOOK')
+DISCORD_BOT_NAME = ENV.fetch('PTO_DISCORD_BOT_NAME')
+
+module Notifier
+  # Service description
+  class UseCaseName
+    def self.notify(*)
+      options = { fetch_options:, dispatch_options: }
+
+      begin
+        use_case = UseCases.use_case_build_function(options)
+
+        use_case.perform
+      rescue StandardError => e
+        { body: { message: e.message } }
+      end
+    end
+
+    def self.fetch_options
+      {
+        base_url: NOTION_BASE_URL,
+        database_id: NOTION_DATABASE_ID,
+        secret: NOTION_SECRET,
+        filter: {
+          filter: { "and": fetch_filter }
+        }
+      }
+    end
+
+    def self.fetch_filter
+      today = Common::TimeZone.set_colombia_time_zone.strftime('%F').to_s
+
+      [
+        { property: 'Desde?', date: { on_or_before: today } },
+        { property: 'Hasta?', date: { on_or_after: today } }
+      ]
+    end
+
+    def self.dispatch_options
+      {
+        webhook: DISCORD_WEBHOOK,
+        name: DISCORD_BOT_NAME
+      }
+    end
+
+    def self.format_options
+      {
+        template: ':beach: individual_name is on PTO'
+      }
+    end
+  end
+end
+```
+
+#### Configure the lambda
+In the `serverless.yml` file, add a new instance in the `functions` block with this structure:
+
+```bash
+functions:
+  ptoNotification:
+    handler: src/lambdas/pto_notification.Notifier::PTO.notify
+    environment:
+      PTO_NOTION_DATABASE_ID: ${file(./env.yml):${env:STAGE}.PTO_NOTION_DATABASE_ID}
+      PTO_NOTION_SECRET: ${file(./env.yml):${env:STAGE}.PTO_NOTION_SECRET}
+      PTO_DISCORD_WEBHOOK: ${file(./env.yml):${env:STAGE}.PTO_DISCORD_WEBHOOK}
+      PTO_DISCORD_BOT_NAME: ${file(./env.yml):${env:STAGE}.DISCORD_BOT_NAME}
+    events:
+      - schedule:
+          name: pto-daily-notification
+          description: "Notify every 24 hours at 8:30 a.m (UTC-5) from monday to friday"
+          rate: cron(${file(./env.yml):${env:STAGE}.PTO_SCHEDULER})
+          enabled: true
+```
+
+#### Deploying
+
+Configure the AWS keys:
+
+```bash
+serverless config credentials --provider aws --key YOUR_KEY --secret YOUR_SECRET
+```
+
+Deploy the project:
+```bash
+STAGE=prod sls deploy --verbose
+```
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Changelog
+
+Features and bug fixes are listed in the [CHANGELOG][changelog] file.
+
+## Code of conduct
+
+We welcome everyone to contribute. Make sure you have read the [CODE_OF_CONDUCT][coc] before.
+
+## Contributing
+
+For information on how to contribute, please refer to our [CONTRIBUTING][contributing] guide.
+
+## License
+
+The gem is licensed under an MIT license. See [LICENSE][license] for details.
+
+<br/>
+
+<hr/>
+
+[<img src="https://github.com/kommitters/chaincerts-smart-contracts/assets/1649973/d60d775f-166b-4968-89b6-8be847993f8c" width="80px" alt="kommit"/>](https://kommit.co)
+
+<sub>
+
+[Website][kommit-website] •
+[Github][kommit-github] •
+[X][kommit-x] •
+[LinkedIn][kommit-linkedin]
+
+</sub>
+
+[license]: https://github.com/kommitters/bas/blob/main/LICENSE
+[coc]: https://github.com/kommitters/bas/blob/main/CODE_OF_CONDUCT.md
+[changelog]: https://github.com/kommitters/bas/blob/main/CHANGELOG.md
+[contributing]: https://github.com/kommitters/bas/blob/main/CONTRIBUTING.md
+[kommit-website]: https://kommit.co
+[kommit-github]: https://github.com/kommitters
+[kommit-x]: https://twitter.com/kommitco
+[kommit-linkedin]: https://www.linkedin.com/company/kommit-co

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/SECURITY.md

@@ -0,0 +1,13 @@
+# Security Policy
+
+## Reporting Security Issues
+
+To report a security issue, you can either:
+- Privately report a vulnerability through repository's Security tab by clicking "Report a vulnerability".
+- Email us at [oss@kommit.co](mailto:oss@kommit.co).
+
+Please, make sure to provide a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
+
+## Responsible Disclosure
+
+If the issue is confirmed as a vulnerability, we will open a Security Advisory and acknowledge your contributions as part of it.