open-index/open-npm huggingface dataset:
npm package: @fionn77/openclaw-monitor-telegram-plugin
Description: Separate monitoring and control plugin for OpenClaw
Latest version: 0.1.0

# Monitor Plugin

Native OpenClaw plugin for out-of-band monitoring and control.

This plugin packages the existing monitor stack as an OpenClaw extension under `~/.openclaw/extensions/monitor-plugin/` and keeps it separate from the main OpenClaw Telegram bot. The monitor bot has its own token, chat id, and allowlist.

Use [IMPLEMENTATION.md](/root/.openclaw/extensions/monitor-plugin/IMPLEMENTATION.md) for the implementation log and setup instructions.

## Distribution

Recommended distribution is npm:

1. Prepare the package in this folder.
2. Run `npm pack` to inspect the publish payload.
3. Publish with `npm publish --access public`.
4. Install on another OpenClaw instance with `openclaw plugins install @fionn77/openclaw-monitor-telegram-plugin`.

Use [PUBLISHING.md](/root/.openclaw/extensions/monitor-plugin/PUBLISHING.md) as the release checklist.

## Telegram

The plugin includes the monitor-bot runtime, polling, commands, reports, and lockdown logic.

It does not create the Telegram bot on Telegram's side. Each installation still needs:

- a bot created in BotFather
- the bot token
- the target chat ID
- allowed Telegram user IDs

Those values belong in `plugins.entries.monitor-plugin.config`.
npm package: @fiori/home-page
Description: This package is a part of [Fiori Tools Extensions](https://www.npmjs.com/package/fiori-tools) project which is set of plugins working on top of [SAP Fiori Tools](https://www.npmjs.com/package/@sap/ux-ui5-tooling) or [UI5 server](https://www.npmjs.com/pack
Latest version: 2.0.15

# Home Page UI5 middleware

This package is a part of [Fiori Tools Extensions](https://www.npmjs.com/package/fiori-tools) project which is set of plugins working on top of [SAP Fiori Tools](https://www.npmjs.com/package/@sap/ux-ui5-tooling) or [UI5 server](https://www.npmjs.com/package/@ui5/server)

## What does it do?

Standard `fiori run` / `ui5 serve` command run http://localhost:8080 serving your static file tree by default. This extension may redirect you to a specifc page from a root path.

In the template provided by Fiori Tools application generator we can see test/flpSandbox.html and test/flpSandboxMockServer.html files. Besides of that we have also sandbox launchpad available as a part of UI5 library and we can take it directly from the test resources. [Fiori Launchpad - Sandbox for application development](https://ui5.sap.com/test-resources/sap/ushell/shells/sandbox/fioriSandbox.html#Shell-home). In addition to that, sandbox launchpad delivers possibility to maintain application config as a separate fioriSandbox.json file which creates even a space to generate it via API.

## How to use

Standard `fiori run`/`ui5 serve` command run just http://localhost:8080 page while may be you want to redirect to a specifc page as a home page. This extension can be used in two modes:

```yaml
server:
  customMiddleware:
    - name: fiori-tools-home-page
      beforeMiddleware: serveIndex
      configuration:
        home_page: path/to/your/home/page.html
        query:
          use-additional-parameter: true
```

or just like this as a shortcut to `home_page: /test-resources/sap/ushell/shells/sandbox/fioriSandbox.html`, delivered by ui5 library itself.

```yaml
server:
  customMiddleware:
    - name: fiori-tools-sandbox
      beforeMiddleware: serveIndex
      configuration:
        query:
          sap_ui_debug: true
```

it is important to remember that /test-reources should be served by your server too, for example using proxy middleware

```yaml
server:
  customMiddleware:
    - name: fiori-tools-proxy
      beforeMiddleware: compression
      configuration:
        ui5:
          path:
            - /resources
            - /test-resources
        url: https://ui5.sap.com
```
npm package: @fiori/types
Description: This package is a part of [Fiori Tools Extensions](https://www.npmjs.com/package/fiori-tools) project which is set of plugins working on top of [SAP Fiori Tools](https://www.npmjs.com/package/@sap/ux-ui5-tooling) or [UI5 server](https://www.npmjs.com/pack
Latest version: 2.0.15

# UI5 Middleware types

This package is a part of [Fiori Tools Extensions](https://www.npmjs.com/package/fiori-tools) project which is set of plugins working on top of [SAP Fiori Tools](https://www.npmjs.com/package/@sap/ux-ui5-tooling) or [UI5 server](https://www.npmjs.com/package/@ui5/server)

Currently it allows to define ui5 middleware with default types:

```typescript
import { UI5_Middleware } from '@fiori/types';

interface Input {
  foo?: string;
  bar?: string;
}

export const yourMiddleware: UI5_Middleware<Input> = function (input) {
  return (req, res, next) => {
    // do something

    next();
  };
};

export default yourMiddleware;
```

## Open issues
Currently it's using types declared in [open-ux-tools project](https://github.com/SAP/open-ux-tools/blob/main/types/ui5.d.ts) developed by SAP, and I'd really wish that those types may become also usable directly via npm package soon. The [issue](https://github.com/SAP/open-ux-tools/issues/1114) has been created for this feature request. Once that package is available may be there will be no need in this package too.
npm package: @fiori/ui5-ts
Description: This extension brings a tiny command which will allow you to serve your TS middleware on your UI5 server without compilation. It's using embedded ts-node esm loader allowing us to resolve _.js references to _.ts files on the fly.
Latest version: 2.0.15

# UI5 Tooling + Typescript

This extension brings a tiny command which will allow you to serve your TS middleware on your UI5 server without compilation.
It's using embedded ts-node esm loader allowing us to resolve _.js references to _.ts files on the fly.

## How to use

`ui5-ts` is nothing more than just `ui5` CLI loaded via ts-node, therefore it has same interface with commands like `ui5-ts serve`.

## Things to remember

- it requires ts-node to be installed globally or as a dependency
- it supports only middlewares developed as ESM modules
- it requires dotenv to init your environment variables from .env file in your cwd