chore: add LICENSES.md file to document dependency licenses

[dylanpulver]

Summary

This PR adds a LICENSES.md file to the repository, which documents the licenses of all dependencies used in the project.

Why This is Important

• Legal Compliance: Having a LICENSES.md file ensures that we are transparent about the licenses of the third-party libraries we use. This helps in maintaining legal compliance and understanding the obligations and restrictions associated with each dependency.
• Transparency: It provides clarity and transparency for contributors, users, and stakeholders about the licensing terms of the software.
• Best Practices: Including a LICENSES.md file is considered a best practice in open-source projects, promoting good governance and trust within the community.

Changes Made

• Generated and added the LICENSES.md file using the pip-licenses tool.

Summary by CodeRabbit

• New Features
  • Introduced a LICENSES.md file that lists third-party libraries used in the project, including their versions and licensing information.
  • Enhanced transparency and compliance with open-source licensing requirements for users and developers.

[coderabbitai]

Walkthrough

A new file named LICENSES.md has been added to the project, detailing third-party libraries used, their versions, and licensing information. This documentation aims to ensure compliance with open-source licensing requirements and provides clarity on the legal terms associated with the libraries utilized in the project.

Changes

Files	Change Summary
LICENSES.md	New file added containing a table of libraries with columns: Name, Version, License.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Project
    participant LICENSES.md

    User->>Project: Request information on libraries
    Project->>LICENSES.md: Retrieve licensing information
    LICENSES.md-->>Project: Provide library details
    Project-->>User: Display library information

Loading

Poem

🐰 In the garden where code does bloom,
A list of licenses clears the gloom.
With versions and names, all neatly aligned,
Open-source treasures, now easy to find!
Hopping with joy, we celebrate this day,
For clarity and compliance, hip-hip-hooray! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 81b40b7 and 66e12a9.

Files selected for processing (1)

• LICENSES.md (1 hunks)

Files skipped from review due to trivial changes (1)

• LICENSES.md

[davidlacho]

This is great! I know there's tooling out there to keep this up to date, too.