Skip to content

Record AGPL for product firmware; security reporting links; Dependabot #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abdullahghani-et merged 1 commit into from
Oct 14, 2026
Merged

Record AGPL for product firmware; security reporting links; Dependabot #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Keeps GitHub Actions used by this repository up to date.
version: 2
updates:
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
3 changes: 2 additions & 1 deletion LICENSING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ applies in its `LICENSE` file.

| What | License | In plain words |
|---|---|---|
| Software, firmware, tools, build layers | [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | Use it, change it, sell it. Keep the notices. Every contributor also grants the patent rights needed to use their work. |
| Product firmware and applications (for example [0700-AAM](https://github.com/MusicTribeOpenSource/0700-AAM)) | [AGPL-3.0-or-later](https://www.gnu.org/licenses/agpl-3.0.html) | Use it, change it, sell it. If you ship or serve a changed version, you publish your changes under the same license. It's also what the JUCE framework requires for open-source use. |
| Other software, tools, libraries and build layers | [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | Use it, change it, sell it. Keep the notices. Every contributor also grants the patent rights needed to use their work. |
| Code built on GPL projects (for example Linux kernel patches, U-Boot) | [GPL-2.0](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html) | Those projects require it. If you share a changed version, you share its source too. |
| Hardware designs (schematics, circuit boards, enclosures) | [CERN-OHL-P-2.0](https://ohwr.org/cern_ohl_p_v2.txt) | Build it, change it, sell it. Keep the notices. |
| Documentation, manuals, images | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) | Reuse it anywhere. Say where it came from. |
Expand Down
9 changes: 7 additions & 2 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,19 @@ Found a vulnerability? Thank you for looking out for everyone.

Report it privately instead:

1. Go to the repository's **Security** tab.
1. Go to the repository's **Security** tab, for example
https://github.com/MusicTribeOpenSource/0700-AAM/security/advisories/new
2. Click **Report a vulnerability**.
3. Describe what you found and how to reproduce it.

GitHub explains the process here:
https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability

Only the repository's maintainers and the organization's owners can see your report.

## What happens next

- We aim to reply within 3 working days.
- We'll keep you updated while we work on a fix.
- We'll keep you updated while we work on a fix, and agree a disclosure date with you.
- We aim to fix confirmed vulnerabilities and publish an advisory within 90 days.
- When it's fixed, we'll credit you in the advisory if you'd like.
Loading