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 FOSSA Status badges to the README
  • Updated formatting in the About section

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two FOSSA Status badges are added to README.md at the top and bottom sections. A minor formatting adjustment changes a bullet prefix from minus to plus in the About section. No functional or structural changes.

Changes

Cohort / File(s)	Summary
Documentation badges and formatting README.md	Added two FOSSA Status badges (top and bottom sections); adjusted bullet prefix in About section from minus (-) to plus (+)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Badges bright and bullets bold,
Documentation stories told,
FOSSA shields now on display,
Formatting improved today! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding FOSSA license scan badges and status indicators to the README.md file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

65-67: Consider consolidating the FOSSA badge placement.

The large FOSSA badge (line 66) duplicates the status already shown by the shield badge (line 11). Having both is redundant—typically one badge suffices for the README. If the large badge is intended to link to a detailed license report, consider either:

• Keeping only the shield badge at the top with a text link to the full FOSSA report.
• Placing the large badge at the end of the README (after the About section) to avoid interrupting section flow.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c3ea4b8 and bdbdc8a.

📒 Files selected for processing (1)

• README.md

🔇 Additional comments (2)

README.md (2)

11-11: FOSSA license scan badge placement looks good.

The shield badge is appropriately placed alongside other status indicators at the top of the README, making license compliance status immediately visible.

Please verify that the FOSSA project URLs are functional and that the badge renders correctly when the README is viewed on GitHub.

---

68-69: Verify the About section formatting change.

The AI summary mentions a formatting adjustment from minus to plus bullet prefix in the About section, but the provided code doesn't clearly show this change. Please confirm that the current formatting at line 69 is correct and intentional.