Skip to content

Third-Party Notices & Licenses

Clean-Core.io is built on and incorporates third-party open-source software and data. We are grateful to their authors. This page provides the required attributions and license references.

Data — SAP Cloudification Repository

Clean-Core.io incorporates data from the SAP Cloudification Repository (github.com/SAP/abap-atc-cr-cv-s4hc), © 2020–2026 SAP SE or an SAP affiliate company and the abap-atc-cr-cv-s4hc contributors.

Licensed under the Apache License, Version 2.0. A copy of the license is available at apache.org/licenses/LICENSE-2.0.

Modifications: the data has been normalized to Clean-Core.io’s internal catalog schema and merged with Clean-Core.io’s own curated mappings, which take precedence.

No NOTICE file: the upstream repository does not ship an Apache NOTICE text file, so Apache-2.0 §4(d) does not apply.


Data — SAP Architecture Center

Clean-Core.io includes metadata of the reference architectures in the SAP Architecture Center (github.com/SAP/architecture-center) — their IDs, titles, last-update dates and archive state — and quotes one passage of the reference architecture RA0001, © 2024 SAP SE or an SAP affiliate company and the architecture-center contributors.

Licensed under the Apache License, Version 2.0. A copy of the license is available at apache.org/licenses/LICENSE-2.0.

Modifications: the metadata is read into Clean-Core.io’s own format; which reference architecture fits which target is Clean-Core.io’s own mapping, not SAP’s. No diagram is included — the reference architectures are linked, not embedded.

No NOTICE file: the upstream repository does not ship an Apache NOTICE text file (checked 10.10.2026), so Apache-2.0 §4(d) does not apply.


Data — SAP documentation on GitHub

Clean-Core.io includes the IDs and titles of SAP communication scenarios extracted from a few documents of SAP’s documentation sources on GitHub (github.com/SAP-docs), © SAP SE or an SAP affiliate company and contributors. In the app, each fact’s mark names the document and the commit it was read from and links to it; an export lists those documents and commits in an attribution section.

Licensed under the Creative Commons Attribution 4.0 International licence (CC BY 4.0), as each repository’s REUSE.toml states; the licence is checked again on every weekly sync. A copy of the licence is available at creativecommons.org/licenses/by/4.0.

Modifications: only the scenario ID, the title the text pairs with it and the product the document is about are extracted; nothing else of the text is kept. Where an exported document uses such a fact, it carries an attribution section naming the source document.


Guidance — DSAG ABAP-Leitfaden

Some rules of Clean-Core.io’s ABAP analysis and generated code are adapted from the “DSAG ABAP-Leitfaden” by DSAG e.V. and contributors, published at 1dsag.github.io/ABAP-Leitfaden from the repository github.com/1DSAG/ABAP-Leitfaden (reviewed at commit 100600df).

Licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0), available at creativecommons.org/licenses/by/4.0.

Changes: translated from German, excerpted, paraphrased and corrected where outdated or inconsistent; metadata and section hashes synced weekly. No image of the guide is reused.

No endorsement: use of the guide does not imply that DSAG e.V. or its authors endorse Clean-Core.io or the way it uses the guide.


Guidance and schemas — SAP reference sources on GitHub

Clean-Core.io uses four SAP repositories on GitHub as references for its ABAP analysis and generated code. Each is synced weekly; what is taken from each is listed per item, with the file or section it rests on.

  • ABAP cheat sheets — github.com/SAP-samples/abap-cheat-sheets (reviewed at commit d43eb13c), © SAP SE or an SAP affiliate company and abap-cheat-sheets contributors.

    Licensed under the Apache License, Version 2.0, available at apache.org/licenses/LICENSE-2.0.

    Reference for ABAP Cloud usage: RAP, application jobs, application logs, mail, XCO and released APIs.

    Changes: Structure followed, no code copied; metadata and hashes synced weekly.

  • ABAP RAP flight reference scenario — github.com/SAP-samples/abap-platform-refscen-flight (reviewed at commit 93f76917), © SAP SE or an SAP affiliate company and abap-platform-refscen-flight contributors.

    Licensed under the Apache License, Version 2.0, available at apache.org/licenses/LICENSE-2.0.

    Reference RAP application (CDS, behavior definitions, access control, authorization, draft) and template for the RAP scaffold.

    Changes: Structure followed, no code copied; metadata and hashes synced weekly.

  • Clean ABAP — github.com/SAP/styleguides (reviewed at commit 6279311f), © SAP SE or an SAP affiliate company and styleguides contributors.

    Licensed under the Creative Commons Attribution 3.0 Unported (CC BY 3.0), available at creativecommons.org/licenses/by/3.0/.

    Rules for generated ABAP.

    Changes: Rules cited and partly enabled through abaplint, paraphrased; no text of the guide is copied; section hashes synced weekly.

  • ABAP file formats — github.com/SAP/abap-file-formats (reviewed at commit e42c8003), © SAP SE or an SAP affiliate company and ABAP file formats contributors.

    Licensed under the MIT License, available at opensource.org/licenses/MIT.

    JSON schemas of the ABAP object types our scaffolds produce, to validate generated object files.

    Changes: Schemas copied unchanged, with the upstream licence notice; metadata and hashes synced weekly.

No NOTICE file: neither Apache-2.0 repository ships an Apache NOTICE text file, so Apache-2.0 §4(d) does not apply.

No endorsement: use of these sources does not imply that SAP SE or the contributors endorse Clean-Core.io or the way it uses them.


Software Components

Clean-Core.io’s primary open-source components, grouped by license. Each component remains under its own license; the full license texts are available in the respective projects.

MIT
nextreactreact-domreact-markdownreact-syntax-highlighterrechartsmermaidmotion@xyflow/react@hookform/resolversmarkeddate-fnsclsxtailwind-mergeexceljsfile-saverjsdomjwks-rsapinopino-prettypostcssautoprefixeresbuildtsx@next/bundle-analyzer
Apache-2.0
firebasefirebase-admin@google/genaiclass-variance-authority
ISC
lucide-react
MPL-2.0 OR Apache-2.0
dompurify
MIT OR GPL-3.0-or-later
jszip

Full Dependency Tree

A CycloneDX SBOM is generated by our security workflow and reviewed per build. Across the production dependency tree, the license inventory breaks down approximately as follows. This is a generated inventory (which may include dual-licensed or undeclared entries), not a legal certification:

License inventory of the production dependency tree
MITComponents540
Apache-2.0Components89
ISCComponents69
BSD-3-ClauseComponents25
BlueOak-1.0.0Components5
BSD-2-ClauseComponents4
Other / dual-licensed / undeclared (MIT-0, 0BSD, CC0-1.0, Unlicense, …)Components14

AI Models

AI processing uses the Google Gemini API. When you use your own key (BYOK), your use is governed by your agreement with Google and Google’s applicable terms.

Trademark Notice: SAP, S/4HANA, ABAP and other SAP product names are trademarks of SAP SE, used for identification and reference only. Clean-Core.io is an independent project and is not affiliated with, or endorsed by, SAP SE (Apache-2.0 §6 grants no trademark rights).

Clean-Core.io v3.0.19 (October 21, 2026)