open-index/open-npm huggingface dataset:
npm package: @osx11/simple-event
Description: Simple custom events
Author: osx11
Latest version: 1.0.4

# TypeScript SimpleEvent

## Example of usage

```typescript
// SomeService.ts

import {SimpleEvent} from '@osx11/simple-event';

let i = 0;
const someEvent = new SimpleEvent<number>();

const callback = (v: number) => {
  console.log(v);
}

someEvent.addEventListener(callback);

setInterval(() => someEvent.emit(++i), 1000);
```

- If you need an event type with `addEventListener` and `removeEventListener` methods only (to prevent unintended emit),
you can use `someEvent.asSubscribeOnlyEvent()`

- To unsubscribe, use `someEvent.removeEventListener(callback)` or modify the code as following:
```typescript
const subscription = someEvent.addEventListener(v => console.log(v));

// run where needed
subscription.unsubscribe()
```
npm package: @osynhq/mcp-server
Description: Osyn MCP local wrapper for Cursor and Windsurf
Author: Osyn HQ
Latest version: 1.1.0

# @osynhq/mcp-server

Osyn MCP (Model Context Protocol) Server - Local wrapper for Cursor and Windsurf AI editors.

## Overview

This package provides a local MCP server that connects your AI editor (Cursor, Windsurf) to the Osyn platform, enabling access to your agreements and organizational data directly from your editor.

## Features

- **Seamless Integration**: Automatically detected by Cursor and Windsurf
- **Secure Authentication**: Token-based authentication with Osyn
- **Real-time Access**: Direct access to your Osyn agreements and data
- **Easy Setup**: One-command initialization

## Installation

No installation required! Use `npx` to run directly:

```bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
```

## Quick Start

### Step 1: Get Your Token

1. Go to your Osyn dashboard
2. Navigate to Settings → Integrations → MCP
3. Generate a new MCP token
4. Copy the token

### Step 2: Initialize Cursor

Run the init command with your token:

```bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
```

This will automatically configure Cursor to use the Osyn MCP server.

### Step 3: Restart Cursor

Close and reopen Cursor. The Osyn MCP server will start automatically.

## Manual Usage

If you prefer to run the server manually:

```bash
npx -y @osynhq/mcp-server serve --token YOUR_TOKEN
```

## Available Commands

### `init`

Configure Cursor to use Osyn MCP:

```bash
npx -y @osynhq/mcp-server init --token YOUR_TOKEN
```

### `serve`

Start the MCP server (usually called automatically by Cursor):

```bash
npx -y @osynhq/mcp-server serve --token YOUR_TOKEN
```

### `test`

Test your connection to Osyn:

```bash
npx -y @osynhq/mcp-server test --token YOUR_TOKEN
```

## Available Tools

Once configured, the following tools are available in your AI editor:

- **`get_agreements`**: Fetch all your agreements
- **`get_agreement_by_id`**: Get a specific agreement by ID
- **`search_agreements`**: Search agreements by keyword

## Configuration

The MCP server configuration is stored in `~/.cursor/mcp.json`.

Example configuration:

```json
{
  "mcpServers": {
    "osyn": {
      "command": "npx",
      "args": [
        "-y",
        "@osynhq/mcp-server",
        "serve",
        "--token",
        "YOUR_TOKEN"
      ]
    }
  }
}
```

## Environment Variables

- `OSYN_SUPABASE_URL`: Override the Osyn backend URL (advanced usage)

## Troubleshooting

### Server not detected in Cursor

1. Make sure you've run the `init` command
2. Restart Cursor completely
3. Check that `~/.cursor/mcp.json` exists and contains the Osyn configuration

### Connection errors

Run the test command to verify your token:

```bash
npx -y @osynhq/mcp-server test --token YOUR_TOKEN
```

### Token issues

- Make sure your token is valid and hasn't expired
- Generate a new token in the Osyn dashboard if needed

## Support

For issues and support:
- Email: support@osyn.io
- Documentation: https://docs.osyn.io
- GitHub: https://github.com/osynhq/mcp-server

## License

MIT
npm package: @osynlig/os-placeloader
Description: A small collection of customizable SVG components to create placeholder loading indicators instead of spinner, like cards loading.
Author: osynlig
Latest version: 0.0.8



# Osynlig Placeloader

A small collection of customizable SVG components to create placeholder loading indicators instead of spinner, like cards loading.

  
## Install
```
npm i @osynlig/os-placeloader --save
```
### How to use
```javascript
import  {  PlaceloaderModule  }  from  '@osynlig/os-placeloader';

@NgModule({
	imports: [
		PlaceloaderModule
	]
});

```
```html
  <os-placeloader speed="2200" primaryColor="rgb(220, 221, 222)" height="74" width="399">
    <svg:g code></svg:g>
  </os-placeloader>

  <os-placeloader speed="2200" primaryColor="#dcddde" height="157" width="399">
    <svg:g facebook></svg:g>
  </os-placeloader>

  <os-placeloader speed="2200" primaryColor="#dcddde" height="120" width="399">
    <svg:g content></svg:g>
  </os-placeloader>

  <os-placeloader speed="2200" primaryColor="#dcddde" height="124" width="399">
    <svg:g list></svg:g>
  </os-placeloader>
```

#### Presets (at the moment...)
  - content
  - facebook
  - list
  - code

## Properties

| | |  | |
|--|--|--|--|
| **speed** | number | `1200` | animation speed |
| **primaryColor** | string | `#dcddde` | placeloader color can be in rgb(), rgba(), hsl(), hsla() or #hex |
| **width** | number | `320` | width of the placeloader |
| **height** | number | `100` | height of the placeloader |

## Development

Fork the repo then clone it
`$ git clone git@github.com:osynligab/placeloader.git`

`cd into the folder`

Install the dependencies
`$ yarn` or `npm i`

Run the demo app
`$ npm start`


## TODO
- Build demo page
npm package: @ot06/be-utils
Description: Backend Utilities Module
Author: Omniscient Tech
Latest version: 0.0.27

# README #

This README would normally document whatever steps are necessary to get your application up and running.

### What is this repository for? ###

* Quick summary
* Version
* [Learn Markdown](https://bitbucket.org/tutorials/markdowndemo)

### How do I get set up? ###

* Summary of set up
* Configuration
* Dependencies
* Database configuration
* How to run tests
* Deployment instructions

### Contribution guidelines ###

* Writing tests
* Code review
* Other guidelines

### Who do I talk to? ###

* Repo owner or admin
* Other community or team contact
npm package: @ot06/express-helpers
Description: Express Helpers for Servers and Resources
Author: Omniscient Technologies
Latest version: 1.0.3

# README #

This README would normally document whatever steps are necessary to get your application up and running.

### What is this repository for? ###

* Quick summary
* Version
* [Learn Markdown](https://bitbucket.org/tutorials/markdowndemo)

### How do I get set up? ###

* Summary of set up
* Configuration
* Dependencies
* Database configuration
* How to run tests
* Deployment instructions

### Contribution guidelines ###

* Writing tests
* Code review
* Other guidelines

### Who do I talk to? ###

* Repo owner or admin
* Other community or team contact
npm package: @ot06/fe-http-client
Description: Simple axios wrapper with list of features required in general scenarios
Author: Omniscient Tech
Latest version: 0.0.10

**Edit a file, create a new file, and clone from Bitbucket in under 2 minutes**

When you're done, you can delete the content in this README and update the file with details for others getting started with your repository.

*We recommend that you open this README in another tab as you perform the tasks below. You can [watch our video](https://youtu.be/0ocf7u76WSo) for a full demo of all the steps in this tutorial. Open the video in a new tab to avoid leaving Bitbucket.*

---

## Edit a file

You’ll start by editing this README file to learn how to edit a file in Bitbucket.

1. Click **Source** on the left side.
2. Click the README.md link from the list of files.
3. Click the **Edit** button.
4. Delete the following text: *Delete this line to make a change to the README from Bitbucket.*
5. After making your change, click **Commit** and then **Commit** again in the dialog. The commit page will open and you’ll see the change you just made.
6. Go back to the **Source** page.

---

## Create a file

Next, you’ll add a new file to this repository.

1. Click the **New file** button at the top of the **Source** page.
2. Give the file a filename of **contributors.txt**.
3. Enter your name in the empty file space.
4. Click **Commit** and then **Commit** again in the dialog.
5. Go back to the **Source** page.

Before you move on, go ahead and explore the repository. You've already seen the **Source** page, but check out the **Commits**, **Branches**, and **Settings** pages.

---

## Clone a repository

Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, [download and install first](https://www.sourcetreeapp.com/). If you prefer to clone from the command line, see [Clone a repository](https://confluence.atlassian.com/x/4whODQ).

1. You’ll see the clone button under the **Source** heading. Click that button.
2. Now click **Check out in SourceTree**. You may need to create a SourceTree account or log in.
3. When you see the **Clone New** dialog in SourceTree, update the destination path and name if you’d like to and then click **Clone**.
4. Open the directory you just created to see your repository’s files.

Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can [push your change back to Bitbucket with SourceTree](https://confluence.atlassian.com/x/iqyBMg), or you can [add, commit,](https://confluence.atlassian.com/x/8QhODQ) and [push from the command line](https://confluence.atlassian.com/x/NQ0zDQ).
npm package: @ot06/rsrc-health
Description: NodeJS Resource: Health
Author: Omniscient Tech
Latest version: 0.1.0

# README #

This README would normally document whatever steps are necessary to get your application up and running.

### What is this repository for? ###

* Quick summary
* Version
* [Learn Markdown](https://bitbucket.org/tutorials/markdowndemo)

### How do I get set up? ###

* Summary of set up
* Configuration
* Dependencies
* Database configuration
* How to run tests
* Deployment instructions

### Contribution guidelines ###

* Writing tests
* Code review
* Other guidelines

### Who do I talk to? ###

* Repo owner or admin
* Other community or team contact
npm package: @ot06/web-http
Description: Web http Client using axios with JWT Authentication & JOSE Encrytion.
Author: Omniscient Technologies
Latest version: 1.0.4

# WEB HTTP

WEB HTTP is a custom http-request package for browser with in-built support for [JOSE (JWE) encryption](https://jose.readthedocs.io/en/latest/#jwe). The ready package for backed could be found at

1. [Express JS(NodeJS)](https://www.npmjs.com/package/@m92/api-crypto)

## Installation and Setup

### [ReactAppBoilerplate](https://github.com/ankitgandhi452/ReactAppBoilerplate)

If you're using [ReactAppBoilerplate](https://github.com/ankitgandhi452/ReactAppBoilerplate) as recommended, requires 4 step configuration:

1. Create Config File

```js
// src/configurations/network/HTTP_CLIENT_CONFIG.js
import API_ROUTES from './API_ROUTES'

const { REACT_APP_ENABLE_CRPTOGRAPHY = '', REACT_APP_API_KEY } = process.env

const ENABLE_CRPTOGRAPHY = REACT_APP_ENABLE_CRPTOGRAPHY.trim().toLowerCase() === 'true'

const HTTP_CLIENT_CONFIG = {
  ENABLE_CRPTOGRAPHY,
  API_KEY: REACT_APP_API_KEY,
  API_ROUTES
}

export default HTTP_CLIENT_CONFIG
```

2. Create Constants File

```js
// src/configurations/network/HTTP_CLIENT_CONSTANTS.js
const { API_TIMEOUT } = process.env

const TIMEOUT = API_TIMEOUT || 3000

const HTTP_CLIENT_CONSTANTS = {
  TIMEOUT
}

export default HTTP_CLIENT_CONSTANTS
```

3. Create HttpClient File

```js
import HttpClientClass from '@m92/http-client-fe-v2'
import HTTP_CLIENT_CONFIG from 'configurations/network/HTTP_CLIENT_CONFIG'
import HTTP_CLIENT_CONSTANTS from 'configurations/network/HTTP_CLIENT_CONSTANTS'

const HttpClient = new HttpClientClass(HTTP_CLIENT_CONFIG, HTTP_CLIENT_CONSTANTS)

export default HttpClient
```

4. Inject HttpClient in Redux Thunk

```js
// src/configurations/redux/store.js
.....
import HttpClient from '//path/to/HttpClient/File'
.....

const middlewares = [
  thunk.withExtraArgument({ HttpClient }) // Argument can be a request object used inside all calls
]
.....
```
## License

MIT