open-index/open-npm huggingface dataset:
npm package: @sap/modules-exploration
Description: SAP Modules Exploration
Author: SAP SE
Latest version: 1.6.10


# @sap/modules-exploration

This is an npm package which provides the ability to explore the available modules/generators installed in a specific predefined folder at runtime.
It provides two main APIs. One to get a list of explored modules and API to display the explored modules to the user in a yeoman-base prompt. <br>

Explored Modules should follow the following guidelines: <br>

1. Installed in /extbin/[MODULES-TYPE] specific folder (e.g generators will be installed in /extbin/generators)
2. Include metadata file: modules.json
   The modules.json for generators should include the following parameters:

```javascript
{
  templates: [
      "name": string, //This name will be displayed in the yeoman-base prompt as part of templates option list. (e.g "SAPUI5 Application")
      "path": string, //Relative path to the template's package. (e.g. "/generators/")
      "features" : [{name : string, values :string[]}], // an array of key-value objects. declares the generator supported features in which this generator can be filtered (e.g [{name:"protocol" : value : ["odataV4"]}])
    }
  ]
}
```

The modules.json for service-provider should include the following parameters:

```javascript
{
  "serviceProviders":[
    {
      "name": string,//This name will be displayed in the yeoman-base prompt as part of service providers option list. (e.g "Steam Punk")
      "path": string, //Path to the service providers package. (e.g. "/extbin/serviceProviders/OdataProviders/SteamPunk-service-provider",
      "features" : [{name : string, values :string[]}], //an array of key-value objects. declares the service-provider supported features in which this module can be filtered (e.g [{name:"protocol" : value : ["odataV4"]}])
      "entryPoint" :{ //The main entry point to trigger the specific service provider logic
         "class" : "ServiceProviderExample ", //The main object
         "method" : "dummyServiceProviderPrompt" //The main method
      }
   }
  ]
}
```


# API

**getExploredModules** <br>
Returns an array of explored modules metadata <br> <br>
the return metatadata is of type ''IModuleInfo[]
**promptExploredModules** <br>
Explores installed modules and prompt their metadata (name) to the user using the given generator. The prompt question can be passed as an input.
If not passed, a generic question will be displayed <br>
npm package: @sap/open-resource-discovery
Description: Open Resource Discovery (ORD) Specification
Author: SAP SE
Latest version: 1.9.10
Deprecated: The package has moved. Use @open-resource-discovery/specification instead.

[![REUSE status](https://api.reuse.software/badge/github.com/SAP/open-resource-discovery)](https://api.reuse.software/info/github.com/SAP/open-resource-discovery)

# Open Resource Discovery Specification

![Open Resource Discovery Logo](./static/img/open-resource-discovery-logo-wide.png "Open Resource Discovery Logo")

## Summary

Open Resource Discovery (ORD) is a protocol that **allows applications and services to self-describe their exposed resources and capabilities**.
It can be used to describe static documentation, but can also reflect tenant specific configuration and extensions (at run-time).​

**To learn more, have a look at the [Open Resource Discovery Specification](https://sap.github.io/open-resource-discovery/) documentation.**

> ℹ ORD is an open standard by SAP, currently geared towards the SAP ecosystem.
> However, it is built to be a generic standard and could be used outside of SAP, if the infrastructure (aggregators, namespace registry) is built or adjusted.
> The standard is extensible through extensibility attributes, custom types and policy levels.

## Communication, Feedback & FAQ

If you have feedback, questions or problems, please create a [GitHub issue](https://github.com/SAP/open-resource-discovery/issues).

## Ownership and Governance

The ORD development is driven by SAP internally, but public feedback, suggestions and contributions are welcome.

## Resources

### Learning Material

Currently there are no public resources beside the ORD spec itself.
We plan to add more in the future.

### Tools and Examples

#### ORD Reference Application

Check out the [ORD Reference Application](https://ord-reference-application.cfapps.sap.hana.ondemand.com/) for an example ORD implementation and how it behaves.

#### ORD Example Data

- Within this repository: [examples/](./examples/).

## History

For detailed and recent changes, please refer to the [CHANGELOG.md](CHANGELOG.md).

## Acknowledgements

- The original idea for ORD came from Harsh Jegadeesan and Divya Mary.
- The currently active core-contributors to the spec are: [Simon Heimler](https://github.com/Fannon), [Sebastian Wennemers](https://github.com/swennemers), [Steffen Göbel](https://github.com/steffengoebel), [Ralf Hofmann](https://github.com/ormos), [Kiril Kabakchiev](https://github.com/KirilKabakchiev), [Nikolay Mateev](https://github.com/NickyMateev), [Bibin Thomas](https://github.com/Bibin-T) and others.

## License

Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/open-resource-discovery).
npm package: @sap/opentelemetry-exporter-for-sap-cloud-logging
Description: A set of auto-configured OpenTelemetry exporters for SAP Cloud Logging
Author: Christian Dinse
Latest version: 0.6.0

[![Version npm](https://img.shields.io/npm/v/@sap/opentelemetry-exporter-for-sap-cloud-logging.svg)](https://www.npmjs.com/package/@sap/opentelemetry-exporter-for-sap-cloud-logging)
[![REUSE status](https://api.reuse.software/badge/github.com/SAP/opentelemetry-exporter-for-sap-cloud-logging-for-nodejs)](https://api.reuse.software/info/github.com/SAP/opentelemetry-exporter-for-sap-cloud-logging-for-nodejs)

# OpenTelemetry exporter for SAP Cloud Logging for Node.js

:warning: **Beta Version**: This package is should not be used in production yet. APIs and functionality may be subject to breaking changes.

## About this project

OpenTelemetry exporter for SAP Cloud Logging is a Node.js package providing a set of auto-configured OpenTelemetry exporters for shipping logs, metrics and traces to [SAP Cloud Logging](https://discovery-center.cloud.sap/serviceCatalog/cloud-logging).

## Requirements and Setup

Check out our [sample app](sample) for details on how to add the provided exporters for logs, metrics and traces to your OpenTelemetry instrumented application.
More details and documentation pages are coming soon.

The package is available on npm and can be installed as follows:

```bash
npm i @sap/opentelemetry-exporter-for-sap-cloud-logging
```

## Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/SAP/opentelemetry-exporter-for-sap-cloud-logging-for-nodejs/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).

## Security / Disclosure
If you find any bug that may be a security problem, please follow our instructions at [in our security policy](https://github.com/SAP/opentelemetry-exporter-for-sap-cloud-logging-for-nodejs/security/policy) on how to report it. Please do not create GitHub issues for security-related doubts or problems.

## Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its [Code of Conduct](https://github.com/SAP/.github/blob/main/CODE_OF_CONDUCT.md) at all times.

## Licensing

Copyright 2024 SAP SE or an SAP affiliate company and opentelemetry-exporter-for-sap-cloud-logging-for-nodejs contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/opentelemetry-exporter-for-sap-cloud-logging-for-nodejs).
npm package: @sap/service-providers
Description: SAP library for service providers
Author: SAP SE
Latest version: 0.3.12

# service-providers

This module provides various service providers:

# Direct URL Service Provider

Provides the ability to consume a service from a URL ( a direct service url rather then through SAP cloud destination service.
The main use case is when creating an application for demo use or for local development when detached from SAP Cloud

# Local Metadata File Service Provider

Provides the ability to use a dummy service represented by metadata.xml file from the local workspace of the developer.
The main use case is when creating an application for demo use and run it with mock data.

# Current Project Service Provider

Provides the ability to consume services from the current CAP project. The service can be java or node.
The main use case is: a developer adds a _UI_ module to _CAP_ project and he wants to bind the UI with a service (java/node) he has in his project.
The flow contains also a change of connectivity details in the `package.json/mta.yaml/xsapp.json`, where we declare the dependencies. Later on, the dependency will be reflected in the `Run Configuration`.

## Requirements

The flow starts and ends in the same behaviour we have for service consumption. 
Additional scenario will be added to the system selection:

    My SAP system
    API hub
    Current project
    Local (will be the next one)

When user selects 'Current project' we should display the all found services from the current CAP project.
</br>The services can be: _Java, Node_.
</br>The format should be: _'service name'_.
</br>Service biding (data connection) - the flow is: binding a service to a UI module, therefore the binding process should be as it is today update service's dependency in the `package.json/mta.yaml/xsapp.json`.
npm package: @sap/sql-interface-specification
Description: SQL interface specification for SAP ecosystem
Author: SAP SE
Latest version: 1.0.2

[![REUSE status](https://api.reuse.software/badge/github.com/SAP/sql-interface-specification)](https://api.reuse.software/info/github.com/SAP/sql-interface-specification)

# SQL interface specification for SAP ecosystem

## About this project

The SQL interface specification for SAP ecosystem defines a standard document format for describing and publishing metadata of database-level API resources of a (database) server to allow consumers to discover API resources and to interact with a server via SQL client interfaces and SQL query or data manipulation statements.

The SQL interface specification for SAP ecosystem is like the Open API specification [1], but for SQL-based APIs instead of REST-based APIs.

[1] The OpenAPI Specification, Version 3.1.0, 2021. https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md

## Versions

The current version is [SQL interface specification for SAP ecosystem 1.0.2](/versions/1.0.2.md).

The corresponding JSON schema is [schemas/v1.0/schema.yaml](/schemas/v1.0/schema.yaml).

Examples are located in the [examples](/examples) folder.

## Requirements

The [scripts](/scripts) folder contains some scripts to validate a SQL interface document, to convert between JSON and YAML representations, and to run the tests of the JSON schema file.

The scripts are based on [Node.js](https://nodejs.org). Before running a script, ensure that dependencies are installed via `npm install`.

## Contributing

This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/SAP/sql-interface-specification/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).

## Security / Disclosure
If you find any bug that may be a security problem, please follow our instructions at [in our security policy](https://github.com/SAP/sql-interface-specification/security/policy) on how to report it. Please do not create GitHub issues for security-related doubts or problems.

## Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its [Code of Conduct](https://github.com/SAP/.github/blob/main/CODE_OF_CONDUCT.md) at all times.

## Licensing

Copyright 2024 SAP SE or an SAP affiliate company and SQL interface specification for SAP ecosystem contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/sql-interface-specification).
npm package: @sap/vite-plugin-leanix-custom-report
Description: Vite plugin for developing SAP LeanIX Custom Reports
Latest version: 8.4.2

# @sap/vite-plugin-leanix-custom-report

A Vite plugin for developing SAP LeanIX Custom Reports with hot reload, TypeScript support, and seamless deployment.

## Features

- 🚀 Fast development with Vite's hot module replacement
- 📦 Automatic bundling and optimization for LeanIX reports
- 🔧 Built-in TypeScript support
- 📤 One-command deployment to LeanIX workspace
- ⚛️ Optimized for React with TypeScript

## Prerequisites

- Node.js 16+ and npm/yarn/pnpm
- A SAP LeanIX workspace with API access
- A valid SAP LeanIX API token

## Get Started

1. Install vite and this plugin with your favorite package manager, here use npm as example:

```bash
npm install vite @sap/vite-plugin-leanix-custom-report
```

2. Create a `vite.config.ts` file in your project root to config vite to actually use this plugin:

```ts
import { fileURLToPath, URL } from 'node:url';
import leanix from '@sap/vite-plugin-leanix-custom-report';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [leanix()],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  },
  build: {
    rollupOptions: {
      input: {
        app: './index.html'
      }
    }
  }
});
```

3. Create an `./index.html` file that will be the entry point to you app:

```html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Vite App</title>
  </head>
  <body>
    <div id="app"></div>
    <script type="module" src="/src/main.js"></script>
  </body>
</html>
```

4. Create an `./src/main.js` file that you can use to add some behavior to your HTML page and/or import a framework such as Vue, React, etc.

5. Add the "upload" command to the "script" section of your `package.json` file:

```json
{
  "scripts": {
    "upload": "vite build --mode upload"
  }
}
```

6. Make sure that the package.json file contains both "author" and "description", and add the "leanixReport" section as follows:

```json
{
  "author": "The report author",
  "description": "Description of the report",
  "leanixReport": {
    "id": "<your report id in dot notation, e.g. leanix.net.report.demo>",
    "title": "Your Report Title",
    "defaultConfig": {}
  }
}
```

7. Finally add a `lxr.json` file into your project root folder with the following contents:

```json
{
  "host": "<your workspace instance here, e.g. demo-eu.leanix.net>",
  "apitoken": "<your workspace api token here>"
}
```

⚠️ **Security Note**: Add `lxr.json` to your `.gitignore` to avoid committing sensitive credentials.

8. You are now ready to start developing your report by issuing the following command

```bash
npm run dev
```

## Troubleshooting

**Common Issues:**

- **Build fails**: Ensure all required package.json fields are present
- **Upload fails**: Verify your API token and workspace URL in `lxr.json`
- **Report not loading**: Check browser console for JavaScript errors
npm package: @sap_oss/odata-library
Description: OData client for testing Netweawer OData services.
Author: SAP SE
Latest version: 2.6.0

# OData library

[![REUSE status](https://api.reuse.software/badge/github.com/SAP/odata-library)](https://api.reuse.software/info/github.com/SAP/odata-library)

A NodeJS library to access OData services provided by the Netweaver server.

## Documentation

Documentation is [here](https://sap.github.io/odata-library/).

## Installation

```shell
$ npm  install @sap_oss/odata-library

```

## Getting Started

```javascript
const Service = require("@sap_oss/odata-library").Service;

let service = new Service(
  "https://username:password@localhost/path/to/service/"
);

service.init
  .then(() => {
    return service.Entity_Set_Name.get(1);
  })
  .then((result) => {
    console.log(result);
  });
```

## Contact Us

```
Jakub Vaclavik <jakub.vaclavik@sap.com>
Michal Nezerka <michal.nezerka@sap.com>
Norbert Volf <norbert.volf@sap.com>
```

## License

Copyright (c) 2020-2021 SAP SE or an SAP affiliate company and odata-library contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/odata-library).
npm package: @sap_oss/task_contrib_types
Description: Type Definitions for Task Providers contributing to the Task Explorer.
Latest version: 4.7.1

# @task-explorer/task_contrib_types

Type Definitions for Task Providers contributing to the Task Explorer.

## Usage

This package exports TypeScript definitions only.
See [api.d.ts](./api.d.ts) for the full list of definitions.

## Support

Open an [issue](https://github.com/SAP/task-explorer/issues) on GitHub.

## Contributing

See [CONTRIBUTING.md](./CONTRIBUTING.md).
npm package: @sap_oss/vscode-mta-tools
Description: VS Code Multi-Target Application tools
Latest version: 1.4.10

[![CircleCI](https://circleci.com/gh/SAP/vscode-mta-tools.svg?style=svg)](https://circleci.com/gh/SAP/vscode-mta-tools)
[![Coverage Status](https://coveralls.io/repos/github/SAP/vscode-mta-tools/badge.svg?branch=master)](https://coveralls.io/github/SAP/vscode-mta-tools?branch=master)
[![Language grade: JavaScript](https://img.shields.io/lgtm/grade/javascript/g/SAP/vscode-mta-tools.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/SAP/vscode-mta-tools/context:javascript)
[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier)
[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
[![dependabot](https://api.dependabot.com/badges/status?host=github&repo=SAP/vscode-mta-tools)](https://dependabot.com/)
[![REUSE status](https://api.reuse.software/badge/github.com/SAP/vscode-mta-tools)](https://api.reuse.software/info/github.com/SAP/vscode-mta-tools)

## Description

The **VS Code Multi-Target Application (MTA) tools** extension is a VS Code extension for development of multi-target applications.
It can be used to build multitarget applications using the [Cloud MTA Build Tool](https://github.com/SAP/cloud-mta-build-tool), to deploy the build result to Cloud Foundry and to create MTA module from template.
The extension is being developed and currently contains limited features.

### Requirements

Make sure that you are familiar with the multi-target application concept and terminology. For background and detailed information, see [Multi-Target Application Model](https://www.sap.com/documents/2016/06/e2f618e4-757c-0010-82c7-eda71af511fa.html).

Make sure the following tools are installed in your environment:

- `GNU Make 4.2.1` or later to build MTA project.
- [Cloud MTA Build Tool](https://github.com/SAP/cloud-mta-build-tool) to build MTA project.
- [Cloud Foundry CLI](https://github.com/cloudfoundry/cli) to work with Cloud Foundry.
- [MultiApps CF CLI Plugin](https://github.com/cloudfoundry-incubator/multiapps-cli-plugin) to deploy MTA archive to Cloud Fountry.
- [MTA tool](https://github.com/SAP/cloud-mta) to add MTA modules.
- [Yeoman-ui extension](https://github.com/SAP/yeoman-ui) to add MTA modules.

### Download and Installation

Import the extension into your Visual Studio Code.
Run `npm install` to install all the needed dependencies.

### Contributing

Contributions are greatly appreciated.
See [CONTRIBUTING.md](https://github.com/SAP/vscode-mta-tools/blob/master/.github/CONTRIBUTING.md) for details.

### Support

Please report [here](https://github.com/SAP/vscode-mta-tools/issues) on any issue.

## Licensing

Please see our [LICENSE](https://github.com/SAP/vscode-mta-tools/LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the [REUSE tool](https://api.reuse.software/info/github.com/SAP/vscode-mta-tools).
npm package: @sap_oss/wdio-qmate-service
Description: [![REUSE status](https://api.reuse.software/badge/github.com/SAP/wdio-qmate-service)](https://api.reuse.software/info/github.com/SAP/wdio-qmate-service)[![Node.js CI](https://github.com/SAP/wdio-qmate-service/actions/workflows/node.js.yml/badge.svg)](http
Author: SAP SE
Latest version: 3.6.2

# Qmate Service
[![REUSE status](https://api.reuse.software/badge/github.com/SAP/wdio-qmate-service)](https://api.reuse.software/info/github.com/SAP/wdio-qmate-service)[![Node.js CI](https://github.com/SAP/wdio-qmate-service/actions/workflows/node.js.yml/badge.svg)](https://github.com/SAP/wdio-qmate-service/actions/workflows/node.js.yml)[![Dependabot Updates](https://github.com/SAP/wdio-qmate-service/actions/workflows/dependabot/dependabot-updates/badge.svg)](https://github.com/SAP/wdio-qmate-service/actions/workflows/dependabot/dependabot-updates)

Qmate Service is a custom WebdriverIO service built in TypeScript for testing web applications and APIs.

## Pages
Please find our official and more detailed documentation [here](https://sap.github.io/wdio-qmate-service/).

## Installation
To install the latest version of the service, simply execute the following command:
```bash
npm install @sap_oss/wdio-qmate-service@latest
```

## Contact
- Benjamin Warth <benjamin.warth@sap.com>
- Marvin Grüßinger <marvin.gruessinger@sap.com>


## License
Copyright (c) 2021-2022 SAP SE or an SAP affiliate company and wdio-qmate-service contributors. Please see our [LICENSE](./LICENSES/Apache-2.0.txt) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/wdio-qmate-service).