Questions people ask

No. It is an independent community project, not affiliated with, endorsed by, or operated by SAP SE. SAP, ABAP, SAPUI5 and Fiori are trademarks of SAP SE. Who runs the atlas is on the imprint.

A directory is a list and a radar is one person’s opinion in rings. The atlas is a graph: artifacts are attached to the capabilities they provide, and posts are attached to the version they were written against. It also says where nothing exists, which a list structurally cannot.

Because popularity is not fit. Download growth rewards age and transitive dependencies, and a package with millions of installs can be a data-leak pattern in a multitenant service. Reach is shown as a fact on every card and is never used as an ordering or an input to a reading.

There is none, deliberately. A single word compresses three questions — is it alive, is it still true, is it worth my time — and loses every case where the answers differ. Instead each artifact carries mechanical readings from one number each, and where a person has written something it answers three fixed questions: what it solves, when not to use it, and what taking it further involves.

CAP is populated first. UI5 and ABAP are open with a thinner artifact layer; BTP/BAIP and HANA are open ahead of their entries; Integration is a domain inside BTP, not a door. It is one graph throughout, so a tool that serves two stacks appears behind both doors without being duplicated.

Who is present for that capability: SAP only, SAP and community together, community only, or nobody yet. Blue is SAP’s hue, violet the community’s, at the same weight. The colour never says who is better — that is answered on each artifact’s page.

No release in over a year. It is a threshold on one crawled number — months since the last release — and the number is shown beside it. Dormant is a reading about the dependency, not about the idea: the page still says what taking it further would involve.

Because origin never influences a reading. The same threshold applies to an official package and to an independent one. Official is a visible facet you can filter by, not a thumb on the scale.

The version of the core the author was using. It is compared with the dated changes the core has made since, and with the config keys the post uses, so the page can say the core moved on this date and this token no longer exists rather than calling the post bad. Old is not wrong; the atlas tells you which parts still hold.

No, and every surface says so. The atlas runs nobody’s code. A recipe carries where it was read and when. A maintainer’s own CI result is crawled and reported as their dated claim, exactly like a star count.

Every claim is dated and sourced. A sentence about what SAP ships links to the page that says so and the day it was last seen saying it. When that date gets old, the rot is visible rather than hidden.

Open a public issue on GitHub, or use the contact form. Every editorial change is a pull request with one author and a dated reason, so a correction lands with its provenance intact.

Yes, as long as it attaches to something — a capability it provides, or one it explains. A link with no edge does not exist here. Facts with sources are welcome; grades are not, since there are none.

Yes. Corrections go through the same pull-request path as everything else. Claiming an entry so that you can edit it yourself is planned; until then, write to us and say which entry.

Yes. Maintainer and author entries come from public sources such as GitHub, npm and the SAP Community. If you would rather not be listed, use the contact form and choose the removal reason. The privacy notice explains what is held and why.

Two ways. Any page fetched by URL is complete in its HTML, so an agent that found it through search gets the readings and the prose without running scripts. For structured use, add the MCP endpoint at /mcp to your client; it answers from the same graph and exposes matching, comparison and checks. The agents page has the tools and how to connect.

Both. Every entry has a JSON file beside its page — /capabilities/caching.json next to /capabilities/caching — and the whole graph is at /graph.json. A plain-text map is at /llms.txt, and the same MCP tools run over HTTP at /mcp. They are advertised through structured discovery only — as a fact about the site, never as an instruction to the model reading it.

No advertising, and no cookie unless you sign in. Page views are counted with Vercel Web Analytics, which sets no cookie and shows the operator only totals, never one reader’s visits. Signing in with GitHub is optional and only keeps what you make in Explore and your orb so they follow you to another browser; nothing is behind it. Fonts are bundled with the site, so no request goes to a font service. The host keeps ordinary server logs; the privacy notice has the detail.

The graph is public on GitHub and every fact in it links to where it came from. A licence for the curated prose has not been declared yet; until it is, ask before republishing the prose. Facts are facts, and credit for the atlas as a source is appreciated. See the terms of use.