Add license scan report and status

[fossabot]

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

• CircleCI
• TravisCI
• Jenkins
• Other

Summary by CodeRabbit

• Documentation
  • Added a FOSSA status shield in the Status section to display license/compliance scan status.
  • Introduced a new License section featuring a prominent FOSSA badge at the end of the README.
  • Improved readability by inserting additional spacing after the NuGet/FAQ area.
  • No functional changes to the application or public APIs; this update is documentation-only.

[coderabbitai]

Walkthrough

Documentation update in README.md adding FOSSA status shield under Status, a new License section with a large FOSSA badge, and inserting two blank lines after the Nuget/FAQ area.

Changes

Cohort / File(s)	Summary of Changes
Documentation updates README.md	Added FOSSA status shield under Status; added License section with large FOSSA badge; inserted two blank lines after Nuget/FAQ area.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble of badges, a hop to the end,
FOSSA now shines where the licenses blend.
Two little spaces for breathing room’s sake,
README refreshed like dew on a lake.
Thump-thump! says the rabbit, quite pleased with the view—
Compliance carrots harvested anew.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • 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.
• 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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

🧹 Nitpick comments (2)

README.md (2)

8-9: Unify badge style and improve accessibility (alt text).

Consider reference-style links to avoid URL duplication and use clearer alt text.

Apply within this hunk:

-[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK?ref=badge_shield)
+[![License scan: FOSSA][fossa-shield]][fossa-link]

Add these link refs once at the bottom of the file (or a dedicated refs block):

[fossa-shield]: https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK.svg?type=shield
[fossa-large]:  https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK.svg?type=large
[fossa-link]:   https://app.fossa.com/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK

---

37-40: License section: mention the project’s license file and trim extra blank lines.

Add a short sentence pointing to LICENSE (if present) and use the same refs to avoid duplicated URLs. Also, one blank line before the header is sufficient.

Proposed edit in-place:

-
-
 ## License
-[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Fhedgehogform%2FCESDK?ref=badge_large)
+If this repository includes a LICENSE file, reference it here for clarity (e.g., MIT). Verify it exists and matches package metadata.
+
+[![License scan: FOSSA][fossa-large]][fossa-link]

If the LICENSE file is missing, would you like me to open a follow-up PR to add one?

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 107e75f and 73fd8e6.

📒 Files selected for processing (1)

• README.md (2 hunks)