Everything in BTP/BAIP
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
Developer-centric command line for SAP HANA
SAP's on-premises agent linking SAP BTP to customer-network systems
AWS agents for ABAP, PI/PO and BW modernisation work
There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.
Developer-centric command line for SAP HANA
CLI adding SAP developer knowledge and MCP servers to AI coding tools
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
SAP's managed environment for building custom agents and workflows
SAP's workspace for conversations, Spaces and directing agents
SAP's Node.js application router in front of business applications
OAuth2 token fetcher for a Cloud Foundry app's XSUAA binding
SAP's on-premises agent linking SAP BTP to customer-network systems
UI5 app and CAP service copying role collections between subaccounts
Quiet No published releases; repository quiet for 54 months.
No license Neither the package manifest nor the repository tree declares a licence.
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
Python agent alerting on SAP AI Core capacity unit consumption
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Log fetcher and parser for one Cloud Foundry app
Merged log tail of every started app in a Cloud Foundry space
AWS agents for ABAP, PI/PO and BW modernisation work
There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
SQLTools connection from a Cloud Foundry app's HANA binding
Runner for Bruno collections against XSUAA-protected CF apps
SAP's Node.js application router in front of business applications
CLI for the SAP BTP Application Frontend service
Node.js inspector tunnel over cf ssh to Cloud Foundry apps
File search in apps deployed to SAP BTP Cloud Foundry over cf ssh
Step-by-step state recorder for one JavaScript function in Node.js
SQL runner against the SAP HANA Cloud database bound to a CF app
Shell debugger for remote Node.js over the Chrome DevTools Protocol
HTTP trace hook streaming a running CF Node.js app's traffic
Cloud Foundry topology cache for the other @saptools packages
SAP's list of released APIs for SAP Cloud ERP with successors
It is a catalogue of SAP's objects and not a reading of your code: it states that an object is not released, never that you used it, and the finding is the ATC check's. For SAP Cloud ERP Private the files exist for feature pack stack releases only, with no update per support package, so a system between two stacks is checked against its stack's file.