open-index/open-npm huggingface dataset:
npm package: @incognia/redoc
Description: ReDoc
Author: Roman Hotsiy
Latest version: 2.1.3-try-it.3

This forks add the features:

1. Environment Selector
2. Try it


These features are located at the `try-it` branch.
Refer to this [commit](https://github.com/inloco/redoc/commit/e72ac21ac7b9de4318c80e844ec933a9e051809c) to see the changes.


OBS: Before deploy a new version, please run: `yarn bundle`
npm package: @incognia/web-sdk
Description: Incognia SDK for the web
Latest version: 1.21.1

![Alt logoImage][logo]

# Incognia SDK

To integrate the SDK, check our [documentation][docs].

[logo]: https://www.incognia.com/hubfs/US/Brand/Logo/logo-incognia-purple.svg
[docs]: https://developer.incognia.com/docs/web/v1
npm package: @incognia/web-sdk-loader
Description: Incognia SDK loader for web applications
Latest version: 1.2.0

![Alt logoImage][logo]

# Incognia SDK Loader

Use the loader to integrate the SDK, check our [documentation][docs].

[logo]: https://www.incognia.com/hubfs/US/Brand/Logo/logo-incognia-purple.svg
[docs]: https://developer.incognia.com/docs/web/v1
npm package: @incognia/web-sdk-types
Description: Incognia SDK type definitions
Latest version: 1.21.1

![Alt logoImage][logo]

# Incognia SDK TypeScript Definitions

This package contains TypeScript definitions for the `window.IncogniaWebSdk` global object. It is only necessary if your project:

- Uses TypeScript; and
- Integrates using a `<script>` tag pointing to the Incognia CDN (instead of https://www.npmjs.com/package/@incognia/web-sdk).

See our [documentation][docs] for more details.

[logo]: https://www.incognia.com/hubfs/US/Brand/Logo/logo-incognia-purple.svg
[docs]: https://developer.incognia.com/docs/web/v1
npm package: @incognitus/client-web-core
Description: Incognitus core web client
Author: Incognitus
Latest version: 1.0.1

# Incognitus Feature Flag (web core)

![Continuous Integration](https://github.com/Incognitus-Io/client-web-core/workflows/Continuous%20Integration/badge.svg)
[![codecov](https://codecov.io/gh/Incognitus-Io/client-web-core/branch/master/graph/badge.svg?token=BNC9RERF0K)](https://codecov.io/gh/Incognitus-Io/client-web-core)
[![npm version](https://badge.fury.io/js/%40incognitus%2Fclient-web-core.svg)](https://badge.fury.io/js/%40incognitus%2Fclient-web-core)

## Integrating Incognitus

## Initializing the service

Before you're able to use the service you'll need to initialize with your tenant and application IDs.

#### index.ts

Initialize Incognitus service

```typescript
import { IncognitusService } from '@incognitus/client-web-core';

const IncognitusService.initialize({
  tenantId: '{your tenant key}',
  applicationId: '{your app id}',
});
```

| Key           | Description               |
| ------------- | ------------------------- |
| tenantId      | Your tenant id            |
| applicationId | The id of the application |

## Checking features

```typescript
import { IncognitusService } from '@incognitus/client-web-core';

const svc = IncognitusService.instance;

const foobar = async () => {
  if (await svc.isEnabled('{feature name}')) {
    return 'new feature text';
  }
  return 'old feature text';
};
```

## Methods

| Method                               | Description                                                 |
| ------------------------------------ | ----------------------------------------------------------- |
| IncognitusService.initialize(config) | Initializes the service (must be called first)              |
| IncognitusService.instance           | The shared instance of the service                          |
| svc.isEnabled(featureName)           | Checks if the flag is enabled                               |
| svc.isDisabled(featureName)          | Check if the flag is disabled                               |
| svc.getFeature(featureName)          | Fetches the feature from the server and returns it's status |
| svc.getAllFeatures()                 | Fetches all features and stores them in the cache           |

## Caching

Currently all known feature flags are cached when the app initializes. New features that are not found
in the cache are retrieved on-demand. The cache stays in place until the app is reloaded or by calling the `getAllFeatures()` method on the service.

### Future Caching Stories

- Save verified cache to local storage
- Provide hard cache refresh (wipe cache if fails)
- Provide soft cache refresh (keep cache if fails)
- Customizable cache refresh times
- Option to disable cache
npm package: @incognitus/vueture-flag
Description: Incognitus feature flag client for VueJS
Author: James Stumme
Latest version: 0.0.8

# Incognitus Feature Flag (VueJS)
[![wercker status](https://app.wercker.com/status/e2077073a54ee8d89ca6bdc356dc2aa1/s/master "wercker status")](https://app.wercker.com/project/byKey/e2077073a54ee8d89ca6bdc356dc2aa1)
[![codecov](https://codecov.io/gh/Incognitus-Io/vueture-flag/branch/master/graph/badge.svg)](https://codecov.io/gh/Incognitus-Io/vueture-flag)

## Integrating Incognitus
Integration of Incognitus into your VueJS application is done in 2 setps.
#### Step 1) main.ts
Install `VuetureFlag` into `Vue`
  ```TypeScript
    Vue.use(new VuetureFlag(), {
        tenantId: You_Tenant_ID,
        applicationId: Your_Application_ID,
    });

    new Vue(
        mixins: [VuetureFlagMixin],
        ...
    ).$mount('#app');
  ```

  Key | Description
  --- | ---
  tenantId | Your tenant id
  applicationId | The id of the application

#### Step 2) App.vue (If you want get the initial features syncronusly)
  Add a conditional render to your `#app` div
  ```html
  <template>
    <div id="app" v-if="$root.vuetureFlag.isInitialized">
  </template>
  ```

## Using in the template
Feature flags can be used to section off a chuck of template.  To do this just add the `v-feature-flag` directive, with the value of your feature flag name in single quotes, to the element you would like to feature flag.  You can also set the feature flag to hide an element when the feature flag is on by adding the modifier `:hidden` to the directive.

Below are a few examples.
```html
<div id="app" v-feature-flag="'Fizzbuzz'">
  <span>Fizzbuzz shown when enabled</span>
</div>
<div id="app" v-feature-flag:hidden="'Foobar'">
  <span>Foobar hidden if enabled</span>
</div>
```

## Caching
Currently all known feature flags are cached when the app initializes.  New features that are not found
in the cache are retrieved on-demand.  The cache stays in place until the app is reloaded.

### Future Caching Stories
* Save verified cache to local storage
* Provide hard cache refresh (wipe cache if fails)
* Provide soft cache refresh (keep cache if fails)
* Customizable cache refresh times
* Option to disable cache
npm package: @incognitus/vuex-test-utils
Description: Testing utilities for Vuex
Author: James Stumme
Latest version: 2.0.3

# Vuex-Test-Utils

![](https://github.com/Incognitus-Io/vuex-test-utils/workflows/Node%20CI/badge.svg?branch=master) 
[![Coverage Status](https://coveralls.io/repos/github/Incognitus-Io/vuex-test-utils/badge.svg)](https://coveralls.io/github/Incognitus-Io/vuex-test-utils)   
This is a collection of test utilities for vuex.  For actions you can check if things are commited or dispatched, and what their payload was.

## Getting started

1. install using `yarn add -D @incognitus/vuex-test-utils`
2. configure `jest.config.js`
```javascript
module.export = {
  setupFilesAfterEnv: ['@incognitus/vuex-test-utils'],
}
```

## Basic useage

```javascript
expect.action(actions.foobar).toCommitWithPayload('foo', 'bar')
```

or

```javascript
expect.action(actions.fizzbuzz).toDispatchWithPayload('fizz', 'buzz')
```

when checking order

```javascript
exect.action(actions.foofizz).toCommitInOrder('foobar', 'fizzbuzz')
```

Things that can be checked are:

* toCommit
* toCommitWithPayload
* toCommitAsRoot
* toCommitInOrder
* toDispatch
* toDispatchWithPayload
* toDispatchAsRoot
* toDispatchInOrder

## Passing action payload and contexts

Payload, state, root state, getters, and root getters can also be passed in with the option parameters on the `expect.action` method

```javascript
// Payload
expect.action(actions.foobar, {foo: bar})

// Context
exect.action(actions.foobar, undefined, {state: {foo: 'bar'}, rootState: {version: '1.0.0'}, etc..})
```
npm package: @incognoir/browser-sdk
Description: Incognoir Browser SDK — Real-time behavioral telemetry for threat detection and intent analysis.
Author: Incognoir Security
Latest version: 1.0.0

# @incognoir/browser-sdk

> Real-time behavioral telemetry SDK for threat detection and intent analysis.

## Installation

```bash
npm install @incognoir/browser-sdk
```

## Quick Start

```javascript
import { init, setUserId } from '@incognoir/browser-sdk';

// Initialize with your environment credentials
init({
  apiBase: 'https://api.incognoir.com',   // Your Incognoir API endpoint
  apiKey: 'your-scoped-api-key',          // From your Admin Console
  environmentId: 'production',            // Your environment ID
});

// Optionally identify the logged-in user
setUserId('user@example.com');
```

That's it. The SDK will automatically:
- Capture mouse movement patterns, typing rhythm, scroll velocity, and click precision
- Send behavioral telemetry to the inference engine every 4 seconds
- Generate unique device IDs and session IDs for tracking

## API Reference

### `init(options)`

Initialize the SDK. Must be called before any other function.

| Option | Type | Default | Description |
|--------|------|---------|-------------|
| `apiBase` | `string` | *required* | Backend API URL |
| `apiKey` | `string` | `''` | Scoped API key |
| `environmentId` | `string` | `'default'` | Environment identifier |
| `debug` | `boolean` | `false` | Enable console logging |
| `intervalMs` | `number` | `4000` | Auto-send interval (ms) |

### `setUserId(userId)`

Associate a user identity with the current session.

### `sendTelemetry(options?)`

Manually trigger a telemetry event (auto-triggered by `init()` on an interval).

### `destroy()`

Stop collecting signals and remove all event listeners.

## What Data Is Collected

The SDK captures **behavioral micro-features** — not content:

| Signal | Description |
|--------|-------------|
| `typing_speed` | Keystrokes per second |
| `scroll_speed` | Scroll velocity (px/s) |
| `cursor_speed` | Mouse movement speed (px/s) |
| `dwell_time` | Time since last interaction |
| `click_count` | Number of clicks in window |

No keystrokes, form data, or personal content is captured.

## License

MIT © Incognoir Security
npm package: @incom/create-bootstrap-theme
Description: Helping package to create new vue components
Author: Gormartsen
Latest version: 1.0.2

# Create Bootstrap Theme
Helps to create css file with color variables

1. Create repository on github:InComNetworking . Example is `vue-bootstrap-theme-dark`.
  Replace **name** with your component name. like `vue-bootstrap-theme-dark`

2. Clone repository localy.

3. Init default component structure.
  You have to run this command from folder above your local folder for repository
  ```
npm create @incom/bootstrap-theme vue-bootstrap-theme-dark

Need to install the following packages:
  @incom/create-bootstrap-theme@1.0.1
Ok to proceed? (y)
? What is the name of the theme package vue-bootstrap-theme-dark
? What is the name of the theme. User friendly. Dark Theme
? How would you descripe theme Dark background based theme
info Created vue-bootstrap-theme-dark/.eslintrc.cjs
info Created vue-bootstrap-theme-dark/.gitattributes
info Created vue-bootstrap-theme-dark/.env
info Created vue-bootstrap-theme-dark/LICENSE.txt
info Created vue-bootstrap-theme-dark/.stylelintrc.json
info Created vue-bootstrap-theme-dark/_gitignore
info Created vue-bootstrap-theme-dark/.editorconfig
info Created vue-bootstrap-theme-dark/README.md
info Created vue-bootstrap-theme-dark/.eslintignore
info Created vue-bootstrap-theme-dark/main.js
info Created vue-bootstrap-theme-dark/style.scss
info Created vue-bootstrap-theme-dark/index.html
info Created vue-bootstrap-theme-dark/vite.config.js
info Created vue-bootstrap-theme-dark/package.json
info Created vue-bootstrap-theme-dark/default.png
info Created vue-bootstrap-theme-dark/dev/InterfaceText.js
info Created vue-bootstrap-theme-dark/dev/CDN.development.js
info Created vue-bootstrap-theme-dark/dev/App.vue
info Created vue-bootstrap-theme-dark/dev/main.js
info Moved vue-bootstrap-theme-dark/_gitignore -> vue-bootstrap-theme-dark/.gitignore
success Initialized empty Git repository
success Installed packages
success Generated into vue-bootstrap-theme-dark

```

4. Start your local dev server:
```
cd vue-bootstrap-theme-dark
npm run dev

  VITE v3.0.2  ready in 363 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose

```

5. Your theme scss code is in  file : style.scss

Next files is help files to develop component:
```
dev:
  App.vue

  main.js
```
npm package: @incomprobable-ui/react
Description: ## Dependencies
Author: Ezequiel Leites
Latest version: 0.0.1

# Incomprobable UI

## Dependencies

- React >= 16.9.0
- React Native >= 0.62.0
- Styled Components >= 4.4.1
- React Native Vector Icons >= 6.4.5

---

## Installation

```bash
# Install the library
yarn add @incomprobable-ui/react
# For React Native, install RNSVG
yarn add react-native-svg
# For React Native, add Souce Sans Pro as custom font
```

---

## Development

```bash
# Clone Repository
git clone https://github.com/Ex-tendeal/incomprobable-ui

# Move to folder
cd incomprobable-ui

# Install library dependencies
yarn install
```

## React Native App

```bash
# Clone Repository
cd stories/native

# Install library dependencies
yarn install
```

---

## Build

### Build for Development

```bash
# Build web bundle
yarn build:dev:web

# Build native bundle
yarn build:dev:native
```

### Build for Production

```bash
# Build web bundle
yarn build:prod:web

# Build native bundle
yarn build:prod:native
```

---

## Running in Local

### Running Web in Local

```bash
# Run in web
yarn storybook:web

# Open Storybook
Navigate to http://localhost:6006
```

### Running Native in Local

```bash
# Run in web
yarn storybook:native

# Open Storybook
Navigate to http://localhost:6006
```
npm package: @inconcept-labs/storage-fallback
Description: Some browsers don't support specific types of storages (localStorage, sessionStorage, etc.) or they may be disabled from browser settings. This library, lets you specify a fallback order, and it will check which storage type is available from the list, an
Latest version: 1.0.0

# @inconcept-labs/fallback-storage

Some browsers don't support specific types of storages (localStorage, sessionStorage, etc.) or they may be disabled from browser settings.
This library, lets you specify a fallback order, and it will check which storage type is available from the list, and use it.  

For example, if you specify `['localStorage', 'sessionStorage', 'cookieStorage', 'memoryStorage']`,
it will use localStorage if it is supported, otherwise it will try the next one and so on.  

For avoiding item key collisions, you can also specify which prefix you want for the storage name.

# Installation
Using npm:
```
$ npm i @inconcept-labs/fallback-storage
```

Using yarn:
```
$ yarn add @inconcept-labs/fallback-storage
```

# Usage
```
import StorageFallback from '@inconcept-labs/fallback-storage';

const prefix = 'cs';
export const cookieStorage = new StorageFallback(prefix, [
  'cookieStorage',
  'memoryStorage',
]);

cookieStorage.setItem('cookie_key', 'cookie_value');
cookieStorage.getItem('cookie_key');
cookieStorage.removeItem('cookie_key');
cookieStorage.removeItem('cookie_key');
cookieStorage.hasItem('cookie_key');
cookieStorage.clear();
```

# Documentation

## Types
`StorageType = 'localStorage' | 'sessionStorage' | 'cookieStorage' | 'memoryStorage'`

## Constructor
### `StorageFallback(storageOrders, prefix)`
Create a storage that stores items with `prefix` prepended and fallback order of `storageOrders`.
#### &nbsp;Parameters
&nbsp;&nbsp;`storageOrders: StorageType[]`  
&nbsp;&nbsp;`prefix: string`
#### &nbsp;Return values
&nbsp;&nbsp;`StorageFallback`

## Instance methods

### `setItem`
Store an item by key
#### &nbsp;Parameters
&nbsp;&nbsp;`key: string`  
&nbsp;&nbsp;`value: string`
#### &nbsp;Return values
&nbsp;&nbsp;None

### `getItem`
Retrieve an item by key
#### &nbsp;Parameters
&nbsp;&nbsp;`key: string`
#### &nbsp;Return values
&nbsp;&nbsp;`string | null`

### `removeItem`
Remove an item by key
#### &nbsp;Parameters
&nbsp;&nbsp;`key: string`
#### &nbsp;Return values
&nbsp;&nbsp;None

### `hasItem`
Determine if the key is present in the storage
#### &nbsp;Parameters
&nbsp;&nbsp;`key: string`
#### &nbsp;Return values
&nbsp;&nbsp;`boolean`

### `clear`
Remove all items from the storage
#### &nbsp;Parameters
&nbsp;&nbsp;None
#### &nbsp;Return values
&nbsp;&nbsp;None

# Gotchas
* `CookieStorage` **has** storage capacity limitations. Also, if browser is closed cookies will be removed.
* `MemoryStorage` does **not** persist between page loads. This is more or less a stop-gap to prevent page crashes, but may be sufficient for websites that don't do full page reloads.
* Using browser native storage *clear* functions will remove your storage data.

# Thanks

[local-storage-fallback](https://github.com/ripeworks/local-storage-fallback) for inspiration

# License

[MIT](LICENSE.md)
npm package: @inconcept-labs/testrail-mcp
Description: MCP Server for TestRail
Author: InConcept Labs
Latest version: 1.0.5

# TestRail MCP Integration

This project provides a Model Context Protocol (MCP) server for integrating with TestRail, allowing to automate test cases using LLM.

## Prerequisites

- Node.js 20 or later
- pnpm 10.7.0 or later
- TestRail instance with API access

## Usage

### Running the server

The server can be run directly using the installed script:

```bash
npx testrail-mcp
```

This will start the MCP server in stdio mode, which can be used with MCP clients that support stdio communication.

### Using with Cursor

In cursor add `.cursor/msp.json` file with the following configuration

```json
{
  "mcpServers": {
    "testrail-mcp": {
      "name": "TestRail MCP",
      "command": "npx",
      "args": ["testrail-mcp"],
      "env": {
        "TESTRAIL_HOST": "https://your-instance.testrail.io",
        "TESTRAIL_USERNAME": "your-email@example.com",
        "TESTRAIL_API_KEY": "your-api-key"
      }
    }
  }
}
```

## License

MIT
npm package: @incoqnito.io/final-form-arrays
Description: Array Mutators for 🏁 Final Form
Author: Erik Rasmussen
Latest version: 3.0.2

# 🏁 Final Form Arrays

[![NPM Version](https://img.shields.io/npm/v/final-form-arrays.svg?style=flat)](https://www.npmjs.com/package/final-form-arrays)
[![NPM Downloads](https://img.shields.io/npm/dm/final-form-arrays.svg?style=flat)](https://www.npmjs.com/package/final-form-arrays)
[![Build Status](https://travis-ci.org/final-form/final-form-arrays.svg?branch=master)](https://travis-ci.org/final-form/final-form-arrays)
[![codecov.io](https://codecov.io/gh/final-form/final-form-arrays/branch/master/graph/badge.svg)](https://codecov.io/gh/final-form/final-form-arrays)
[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier)

Mutators for updating array fields in
[🏁 Final Form](https://github.com/final-form/final-form).

---

## [Getting Started](https://final-form.org/docs/final-form-arrays/getting-started)

## [API](https://final-form.org/docs/final-form-arrays/api)