Person
aesatiroglu
GitHub@satiroglulast push
Capabilities
Provides
Frontend performanceUI5Frontend performanceFinding why a browser UI is slow to start or to respond, and what to change: how many requests it sends and whether they block each other, how large its bundles are, and which OData round trips it waits on. Distinct from [query profiling](capability:query-profiling), which starts at the service and the database rather than at the browser's network log.LintingUI5LintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.
Entries
Group by
EntrySignals
Maintains
@satiroglu/kaev@satiroglu/kaevA command line that runs rule-based checks over a SAPUI5 or OpenUI5 project, reporting each finding with a rule id, a category, a severity, a confidence and the file it sits in.independent, ui5
Not in a project whose dependencies must all carry an open-source licence: KAEV is proprietary software, its licence page states that downloading or viewing the npm package does not by itself grant permission to use, copy, modify, redistribute, sublicense, sell, host or create derivative works, and the LICENSE file shipped with the package carries the controlling terms. Not as the last word on whether a UI5 application is secure: its rule reference states that a heuristic finding is not proof of a vulnerability, and its documentation puts professional security review beside it rather than under it.
Rule-based checker for SAPUI5 and OpenUI5 projects
Details
History
- @satiroglu/kaevThe repository the npm record declares is now reachable. It returned 404 on 2026-09-30, 2026-10-01 and 2026-10-02; today it answers, as a public repository created on 2026-09-16 and last pushed on 2026-09-30, not a fork, carrying `src`, `tests`, `scripts`, `docs`, the README and the LICENSE file, with GitHub reading the licence as NOASSERTION. `source_available` moves to true with it: `src/index.ts` and the directories under it are the TypeScript the tool is built from, so there is source to read. The licence has not changed and grants no rights to use it — the README states "Public npm publication makes package contents downloadable and inspectable; a proprietary license restricts legal rights but does not technically hide those contents." — which is why `identity.license` stays "Proprietary" and `when_not_to_use` stands as written.
- @satiroglu/kaevThe one key the `cli` type owns (TYPE_PROPERTIES in vocab.json), stated from the README's CI/CD section, "npm install --save-dev @satiroglu/kaev", and the installation page, which gives the same command for a project-level install beside `npx @satiroglu/kaev@latest` and a global install. The installation page's "Package installation requires registry access. Project analysis itself runs offline." is the second sentence it rests on: the registry is how the command arrives and the only thing it needs the network for.
- @satiroglu/kaevThe dependency the entry could not point at before. [@ui5/linter](artifact:ui5-linter) is pinned at 1.23.7 in the npm record's dependencies and the README states "Integrates the official `@ui5/linter` in a restricted child process", so the edge is the maker's own statement; the `for` sentence carries the conditions the rule reference puts on the adapter rather than on the dependency, which ships with every install. Written now because the artifact exists to point at: it was not in the graph when this entry was drafted, and the prose link in `what_it_solves` moves from the repository address to the entry with it.
- @satiroglu/kaevReinstating the condition dropped yesterday, with the half neither version carried. The README does say only "The official UI5 Linter adapter currently applies to application roots", but the rule reference, read again live today, states it in full: "The adapter runs only for applicable application roots with a manifest; legacy manifest-less projects remain analyzable with native KAEV rules." That page is one of the two this entry already cites for the linting edge, so the condition rests on a source already on the record. The same page's "Use --no-ui5-lint only when partial coverage is intentional." replaces the earlier reading that a run marks coverage partial.
- @satiroglu/kaevStated rather than left absent. The licence page says "KAEV is proprietary software. No open-source license is granted.", and the repository the npm record declares, git+https://github.com/satiroglu/kaev.git, returned 404 on 2026-09-30, on 2026-10-01 and again today, so there is no source to read and the entry now says so instead of staying silent. The same page's "Public npm publication makes packaged files downloadable and inspectable. A proprietary license restricts legal rights but does not technically hide package contents." is about the published tarball, whose `bin` is the build output `dist/cli/cli.js`, and not about source anyone may read, so it is recorded here rather than carried as a true value.
- @satiroglu/kaevkaev.org groups one of its four categories as "Performance & OData" and the rule reference carries the rows behind it, so the tool answers [frontend performance](capability:frontend-performance) as well as [linting](capability:linting), by static rule over the project's own code. That capability's reading says the core stops at configuration and the build and sends the reader to the browser's developer tools for the network log, which is the half these rules read statically instead. It was assessed core-only on 2026-09-14 and holds no provides edge from any artifact today, so this is the first one on it, and the state needs the same re-assessment as linting's.
- @satiroglu/kaevThe manifest condition was not the README's claim. It states "The official UI5 Linter adapter currently applies to application roots" and "Integrates the official `@ui5/linter` in a restricted child process", so the condition came out and the child process went in. All seven sources were re-read on 2026-10-01 and every quote still stands word for word; 0.3.0, published 2026-09-30, is still the latest version, and github.com/satiroglu/kaev returned 404 again.
- @satiroglu/kaevHanded over as three URLs. Typed `cli` because what is published is a command with a `kaev` bin entry, run in a project directory rather than installed into a UI5 build; `independent` because the site states "Independent developer tool. Not affiliated with or endorsed by SAP." It answers [linting](capability:linting) on the UI5 door, where the graph already reads UI5 linter as the core's answer and KAEV's own documentation names that linter as something it runs alongside its own rules — and it would be the first provider that capability holds on that door, whose coverage was assessed core-only on 2026-09-14 with a note saying the graph holds no UI5 provider. No repo link: the repository field of the npm record points at github.com/satiroglu/kaev, which still returned 404 on 2026-09-30, so the entry is reachable through npm, the site and the documentation. `when_not_to_use` states the proprietary licence and the heuristic disclaimer, both from the maker's own pages; `identity.license` is "Proprietary" because the npm record says "SEE LICENSE IN LICENSE" and the licence page says no open-source licence is granted.
- First entry seenDiscovered via Added by hand.
For your agent
- Ref
actor:satiroglu- JSON
- /actors/satiroglu.json
- MCP
- Connecting an agent