2026-10-15karma-ui5-transpilelifecycle → deprecatedThe README's own notice, which the description already paraphrased, was not recorded as the maker's dated statement. It is quoted here and shown as plain text: the maintainer's claim, not a reading and not a tier.
2026-10-15karma-ui5-transpileprovides[capability:ui5-testing] → two quoted sources and the coverage_report propertyThe edge cited the README without a sentence. Coverage is the reason this preprocessor exists for a TypeScript project, and it is the comparison the capability now declares; the README states it in its own words.
2026-10-15karma-ui5-transpiledescription.what_it_solves → The same sentence, with why karma-ui5 is needed.The README calls the karma-ui5 plugin obligatory and says the configuration is read from it, which is what makes it a prerequisite rather than a companion.
2026-09-27cds-plugin-ui5description.what_it_solves → A CDS server serves the files under `app/`. A UI5 CLI project is not a folder of files ready to serve: its framework resources are resolved and its middlewares configured by `ui5.yaml`, and until something runs that chain the project needs a server of its own. This plugin runs it inside the CDS server, for a project in `app/`, in the folder `cds.env.folders.app` names, or added as a dependency of the CDS server. Each project is mounted under a path derived from the `metadata/name` of its `ui5.yaml`, overridable in the `ui5.yaml` itself, in the CDS server's `package.json` or through `CDS_PLUGIN_UI5_MODULES`. In a project it is one development dependency and an existing `ui5.yaml`, on [@sap/cds](artifact:sap-cds) 6.8.2 or higher.The paragraph claimed live transpiling, which the README does not mention, and said nothing about the two facts a reader needs: where a project has to sit and what it has to be. Rewritten from the README's own sentences. capire's plugin list is where the transpiling claim comes from, and it is quoted on the capability instead of asserted here.
2026-09-27cds-plugin-ui5provides → capability:ui5-dev-server, with what_it_does, sources and two facet valuesThe edge was a bare ref, so the page said the plugin answered the capability and nothing about how. The README supplies both facet answers and the mount-path behaviour.
2026-09-27cds-plugin-ui5compat.cds_range → >=6.8.2The README states the floor: "The plugin requires [`@sap/cds`](https://www.npmjs.com/package/@sap/cds) `>=6.8.2`."
2026-09-27cds-plugin-ui5flavors → nodeThe README's opening sentence says it is a cds-plugin for the node runtime, so the flavor is stated rather than derived from the artifact type.
2026-09-27cds-plugin-ui5identity.license, source_available → Apache-2.0, trueRead from the package's own README licence section, as its siblings in the same repository already record.
2026-09-27ui5-middleware-capdescription.what_it_solves → A UI5 CLI project's dev server serves the app, and the CAP services it calls run in a second process started and stopped on its own. This middleware calls `cds serve` and embeds the express middlewares it returns into the UI5 dev server, so one command answers both: it is entered under `server/customMiddleware` in `ui5.yaml`, where `mountPath` sets the url the CDS server answers on and `moduleId` names the npm package the CDS server is loaded from. Its default options are `with-mocks` and `in-memory?`, which start in-process mock services for required services that have no external binding and add a transient in-memory database bootstrapped on each restart. It is the counterpart of [cds-plugin-ui5](artifact:ui5-community-cds-plugin-ui5), which embeds the other way round, the UI5 CLI middlewares inside the CDS server; the repository's own comparison of the six tools that connect a UI5 app to a backend lists both, and separates them on which of the two embeds the CAP server. In a project it is one development dependency of the UI5 project, on [@ui5/cli](artifact:sap-ui5-cli) 3 or higher.The old paragraph said the registry description was the only documentation published and that no README states how it is configured. The package does publish one, with Prerequisites, Usage and a Configuration options section: "- `options`: `<object>` (default: `{ "with-mocks": true, "in-memory?": true }` )", alongside `moduleId` and `mountPath`. Rewritten from that README, and the counterpart named, since the two tools embed in opposite directions.
2026-09-27ui5-middleware-capdescription.one_line → UI5 CLI middleware that runs a CDS server inside the UI5 dev server, mounted at a path the UI5 project configures.Nothing in the documentation says the dev server is driven by a backend; the README and the docs site both say a CDS server is embedded inside the dev server, and the `mountPath` option is where it answers: "`ui5-middleware-cap` improves the development experience for the [SAP Cloud Application Programming Model (CAP)](https://cap.cloud.sap/docs/about/) by embedding a CDS server inside the UI5 dev server."
2026-09-27ui5-middleware-capprovides → capability:ui5-build-tooling, with what_it_does and the README's own sentences on the middleware, mountPath and moduleIdThe edge rested on the npm one-liner alone, so the page said the middleware embeds the CDS middlewares and nothing about where the server answers or where it is loaded from. Both are stated in the README's Configuration options section.
2026-09-27ui5-middleware-capalternative_to → artifact:ui5-community-cds-plugin-ui5The maintainers publish the two as members of one set and compare them in one table. The repository README: "Six tools in this repo can connect a UI5 app to a backend (`cds-plugin-ui5`, `ui5-middleware-cap`, `ui5-middleware-approuter`, `@sap/approuter`, `dev-approuter`, `ui5-middleware-simpleproxy`)." The comparison in docs/backend-connectivity.md is what separates this pair: "| Embeds CAP server | ❌ | ✅ | (✅)¹ | ❌ | ✅ | (✅)¹ |", the first two columns being cds-plugin-ui5 and ui5-middleware-cap. The inverse edge is derived, so cds-plugin-ui5 shows it without being edited.
2026-09-27ui5-middleware-capcompat → runtimes node, cds_range >=6.8.1The package manifest declares the floors, "@sap/cds": ">=6.8.1" and "@ui5/cli": ">=3" in peerDependencies, and the README's opening sentence puts it at "the node runtime of the SAP Cloud Application Programming Model (CAP)". On the UI5 door runtimes is how the tool runs and is never read as a flavor.
2026-09-27ui5-middleware-caprequires → artifact:sap-cds, artifact:sap-ui5-cliBoth are stated by the README rather than read off a dependency list: it calls `cds serve` internally to build the middleware functions, and "All releases of this UI5 CLI extension using the major version `3` require UI5 CLI V3." The peerDependencies ranges are quoted beside each edge.
2026-09-27ui5-middleware-capidentity.author, maintainers → Peter Muessig, actor:petermuessig and actor:ui5-communityThe package manifest names the author, "author": "Peter Muessig". The entry recorded him as a contributor only, which is the weaker claim; cds-plugin-ui5 in the same repository already carries both.
2026-09-09cds-plugin-ui5contributors → actor:petermuessigTwo actor files carried the same GitHub login. peter-m-ssig was keyed on a slugified display name — the umlaut in "Peter Müssig" drops out of the slug, so it looked nothing like the crawled petermuessig and nobody spotted the double. Merged onto the login, which is the identity the crawl matches on.
2026-08-31cds-plugin-ui5origin_ring → community-orgui5-community is the UI5 ecosystem's community org, the counterpart of cap-js-community. It was absent from the owner table because that table only knew CAP, so this fell through to independent. Found by probing UI5.
2026-08-31First entry seenDiscovered via Added by hand, npm registry, capire · plugins.

For your agent

Ref: actor:petermuessig
JSON: /actors/petermuessig.json
MCP: Connecting an agent