Add EU AI Act

[carloshvp]

https://github.com/GenAI-Gurus/awesome-eu-ai-act#readme

EU regulation governing the development and deployment of artificial intelligence systems, establishing a risk-based compliance framework with obligations phasing in through 2027.

PRs reviewed:

• Add Microsoft Agent Framework #4003
• Add AI Evaluation #3923
• Add Agent Skills #3888
• Add Human Activity Recognition #4016

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself.
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days. Repository created January 8, 2024.
• Is not AI-generated.
• Run awesome-lint on your list and fix the reported issues. ✅ Passes with 0 errors.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme.
• It's the result of hard work and the best I could possibly produce.
• The repo name of your list should be in lowercase slug format: awesome-eu-ai-act.
• The heading title of your list should be in title case format: # Awesome EU AI Act.
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. ✅ Both set.
• Not a duplicate. No existing EU AI Act awesome list exists.
• Only has awesome items. Curated, not exhaustive.
• Does not contain items that are unmaintained, archived, or deprecated.
• Includes a project logo/illustration whenever possible.
• Entries have a description, ending with a period.
• Includes the Awesome badge.
• Has a Table of Contents section named Contents as the first section.
• Has an appropriate license. CC0.
• Has contribution guidelines in CONTRIBUTING.md.
• Has consistent formatting and proper spelling/grammar.
• Does not use hard-wrapping.
• Does not include a CI badge.
• Does not include an "Inspired by awesome-foo" link.

[carloshvp]

unicorn

[carloshvp]

Following up with improvements based on feedback:

Completed

• Added repository description: "Curated tools, official sources, OSS, templates, and guides for EU AI Act compliance."
• Set homepage URL pointing to the readme
• Added 13 GitHub topics: eu-ai-act, ai-compliance, ai-governance, responsible-ai, trustworthy-ai, ai-policy, regtech, risk-management, compliance, open-source, awesome-list, artificial-intelligence, european-union
• Enabled GitHub Discussions for community Q&A
• Added a "Start Here" prompt in the readme to guide first-time visitors to the official full text, compliance checker, and templates sections
• Fixed maintainer name spelling throughout

In progress

• Social preview image (1280x640, EU AI Act branding)
• Pinned welcome Discussion post to orient new contributors

[johnxie]

Reviewing per the submission requirements:

Issues found in the list (https://github.com/GenAI-Gurus/awesome-eu-ai-act):

1. Extra badges beyond the Awesome badge — The README heading includes [![PRs Welcome]...], [![Last Commit]...], and [![License: CC0]...] badges alongside the Awesome badge. The guidelines advise against CI and extra dynamic badges. The "Last Commit" badge in particular shows live repository state (similar to a CI badge) which the guidelines explicitly disallow. Consider removing all badges except the required Awesome badge.

2. Author byline in the description position — The line > Maintained by **[Carlos Hernandez]... appears in the blockquote position (where the succinct theme description should be), before the actual topic description. The opening blockquote should be a clean one-sentence description of the topic (EU AI Act), not maintainer attribution. Move the maintainer credit to a Footnotes section instead.

3. License detection — GitHub shows NOASSERTION for the license despite the CC0 badge. Ensure the LICENSE file content matches a format GitHub can auto-detect as CC0 (e.g. use the standard CC0 1.0 Universal template from https://creativecommons.org/publicdomain/zero/1.0/legalcode).

The content quality and topic coverage look solid — these are formatting issues that should be straightforward to fix.

[carloshvp]

Thanks for the thorough review. All three issues are fixed:

1. Extra badges - removed. Only the Awesome badge remains in the heading.
2. Author byline - moved to a ## Footnotes section at the bottom of the readme. The opening description now goes straight to the topic.
3. LICENSE detection - replaced with the canonical CC0 1.0 Universal template (starting with "Creative Commons Legal Code") which GitHub's licensee library detects correctly.

All changes pass npx awesome-lint with zero errors.

[carloshvp]

Additional review posted: #3952 (comment) (Add Performance Engineering)

[carloshvp]

Two more improvements completed:

• Social preview image added (1280x640, EU AI Act branding)
• GitHub Discussions enabled for community Q&A and resource suggestions

[weilun88313]

Review of awesome-eu-ai-act:

1. License shows NOASSERTION on GitHub despite the LICENSE file containing CC0 text. GitHub fails to auto-detect it — likely because the file doesn't match GitHub's exact CC0 template byte-for-byte. Consider re-creating the LICENSE file using GitHub's template picker (/community/license/new?branch=main&template=cc0-1.0) so the repo metadata correctly shows CC0.

2. The "Footnotes" section contains maintainer attribution that reads as self-promotion. "Maintained by Carlos Hernandez... Founder of GenAI Gurus — Europe's GenAI community (2,000+ members)" reads more like marketing. Per the guidelines, Footnotes should contain "non-important but necessary content (like extra copyright notices, hyperlinks to sources)." Consider trimming it to just the name/link without the community-size qualifier.

3. The top description is not in blockquote format. Most awesome lists use a > blockquote for the succinct description right after the heading. The "Key compliance deadlines" bullet list and the "Want to contribute?" / "New to the EU AI Act?" paragraphs before Contents add significant preamble — consider moving those into the body of the list rather than above Contents.

4. Overall well-structured. Contents section is clean (named "Contents", one level of nesting, no Contributing/Footnotes entries), entries have descriptions ending with periods, and CC0 + CONTRIBUTING.md are present. Main actionable item is the license detection fix.

[carloshvp]

All three issues fixed (commit GenAI-Gurus/awesome-eu-ai-act@4921489):

1. License detection — replaced the LICENSE file with GitHub's canonical CC0 1.0 Universal template (fetched via /licenses/cc0-1.0 API endpoint). The byte-for-byte match now allows GitHub's licensee library to detect it correctly.
2. Footnotes — removed the community-size qualifier. Now reads: "Maintained by Carlos Hernandez (GitHub @carloshvp)"
3. Description structure — the opening paragraphs are now a single blockquote immediately after the heading, as the guidelines expect. The compliance deadlines and start-here guidance have been moved into the Contributing section.

Passes npx awesome-lint with 0 errors.

[Simply007]

Awesome initiative @carloshvp - already useful.

You might want to turn the releases and packages off on the repo.

[carloshvp]

@Simply007 : thanks for the idea. Done. I also removed the "Deployments", though it was not visible.

[Harsh9005]

The repo itself is solid (CC0, badge, topics, lint output) but two structural things stood out reading through.

Consultancies & Service Providers stretches what an Awesome list normally curates. The manifesto talks about "the best", and a list of consultancies tends to drift into a vendor directory — even with rigorous selection it is hard to verify that any given consultancy is the best the way you can verify a tool or a piece of legislation. Worth thinking about whether the section serves readers or just lists firms. If you keep it, an inclusion criterion in a section intro would help (specific AI Act case work? client references? recognised certification?).

The other thing is the h3 subsections sitting inside several h2 categories (Regulation Text inside Official EU Sources, and similar elsewhere). The TOC only shows h2 headings, so a chunk of structure is invisible to anyone scanning the contents page. Either promote the important h3s into the TOC, or fold them into a brief prose intro under the parent h2 so the visible structure matches the real one.

Small wording note. Templates & Checklists reads ambiguously. Templates of what, written by whom? A one-line intro under that heading would clarify the bar.

[carloshvp]

Thanks for the thoughtful review. I addressed these points in GenAI-Gurus/awesome-eu-ai-act@d74607f:

1. Removed Consultancies & Service Providers to avoid the list drifting into a vendor directory.
2. Expanded the Contents section so the h3 subsections are visible and easier to scan.
3. Added a short intro under Templates & Checklists to clarify the scope.

The repo still passes npx awesome-lint with 0 errors.

[carloshvp]

Quick status check for maintainer review:

• Required 4 PR reviews are completed and listed in the PR body.
• All reviewer feedback in this thread has been addressed.
• The repo license is detected as CC0.
• Only the Awesome badge remains.
• The opening description, Contents, Footnotes, and entry formatting have been cleaned up per feedback.
• npx awesome-lint passes with 0 errors.

No rush, but I believe this is ready for a maintainer pass whenever it reaches the queue.