open-index/open-npm huggingface dataset:
npm package: @msolorio_org/package_0
Description: A public organization scoped package hosted on the npm registry.
Author: Michael Solorio
Latest version: 1.5.0

# @msolorio_org/package_0

A public organization scoped package hosted on the npm registry.

# Steps for publishing to npm registry

## Setup
- Set as a git repository and add a git remote
- Create an npm package scoped to the organization
  - `npm init --scope=@my-org`
- Create a `README.md` for package 
- `"type": "modules"` should be set in `package.json` if using ES6 modules
- set the main entry point for package
- Compile typescript code if needed. Packages are generally accessed through compiled javascript code.
- Create a `.npmignore` file to exclude src, node_modules, git, ts, etc. from the npm package when it is published.
- `npm install`
- `npm run build` to compile if needed

## Test
- Test your package by installing it into another project with the full path to your package
  - `npm install <path/to/package>`

## Publish
Push code to source control first.

By default npm packages are published with private access

publish with public access
- `npm publish --access public`
npm package: @msomsina/i18n-manager
Description: A powerful i18n management tool for handling translations
Author: msomsina
Latest version: 1.0.12

# i18n-manager

A powerful tool for managing translations in your project.

## Installation

### Global Installation

```bash
npm install -g @msomsina/i18n-manager
```

### Local Installation

```bash
npm install @msomsina/i18n-manager
```

## Usage

### Global Usage

After global installation, you can use the tool from anywhere:

```bash
i18n-manager <command> [options]
```

### Local Usage

After local installation, you can use the tool in your project:

```bash
npx i18n-manager <command> [options]
```

### Global Options

- `-p, --path <path>` - Path to translations directory (default: "src/assets/i18n")
- `-b, --base-lang <lang>` - Base language code (default: "en")

### Commands

#### Create New Language

```bash
i18n-manager create <language-code> [--path <path>] [--base-lang <lang>]
```

Example:
```bash
# Using default path and base language (src/assets/i18n, en)
i18n-manager create fr

# Using custom path
i18n-manager create fr --path src/assets/i18n

# Using custom base language
i18n-manager create fr --base-lang ru
```

This will create a new translation file `fr.json` with the same structure as your base language file.

#### Sync Translations

```bash
i18n-manager sync [--path <path>] [--base-lang <lang>]
```

Example:
```bash
# Using default path and base language
i18n-manager sync

# Using custom path
i18n-manager sync --path src/assets/i18n

# Using custom base language
i18n-manager sync --base-lang de
```

This will sync all missing translations with the base language file.

#### Check Translations

```bash
i18n-manager check [--path <path>] [--base-lang <lang>]
```

Example:
```bash
# Using default path and base language
i18n-manager check

# Using custom path
i18n-manager check --path src/assets/i18n

# Using custom base language
i18n-manager check --base-lang es
```

This will check for missing translations in all language files.

## License

MIT
npm package: @msonnb/pds
Description: Reference implementation of atproto Personal Data Server (PDS)
Latest version: 0.4.208

# @atproto/pds: Personal Data Server (PDS)

TypeScript reference implementation of an atproto PDS.

[![NPM](https://img.shields.io/npm/v/@atproto/pds)](https://www.npmjs.com/package/@atproto/pds)
[![Github CI Status](https://github.com/bluesky-social/atproto/actions/workflows/repo.yaml/badge.svg)](https://github.com/bluesky-social/atproto/actions/workflows/repo.yaml)

If you are interested in self-hosting a PDS, you probably want this repository instead, which has a thin service wrapper, documentation, a Dockerfile, etc: https://github.com/bluesky-social/pds

## License

This project is dual-licensed under MIT and Apache 2.0 terms:

- MIT license ([LICENSE-MIT.txt](https://github.com/bluesky-social/atproto/blob/main/LICENSE-MIT.txt) or http://opensource.org/licenses/MIT)
- Apache License, Version 2.0, ([LICENSE-APACHE.txt](https://github.com/bluesky-social/atproto/blob/main/LICENSE-APACHE.txt) or http://www.apache.org/licenses/LICENSE-2.0)

Downstream projects and end users may chose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0.
npm package: @mspcopilot/n8n-nodes-unifi-sitemanager
Description: n8n community node to work with the UniFi Site Manager API
Author: Dan Buhler
Latest version: 0.1.2

# n8n-nodes-unifi-sitemanager

This is an n8n community node. It lets you use UniFi Site Manager in your n8n workflows.

I built it to test out declarative n8n nodes, but wanted to share it. Shoutout to [r/msp](https://www.reddit.com/r/msp/). You can reach me at [u/j0dan](https://www.reddit.com/user/j0dan/) there.

## Operations

### Hosts
- **Get Many** - Retrieve a list of many hosts associated with your UI account.
- **Get** - Get detailed information about a specific host by ID

### Sites
- **Get Many** - Retrieve a list of many sites from hosts running the UniFi Network application

### Devices  
- **Get Many** - Retrieve a list of UniFi devices managed by hosts where your UI account is owner or super admin
  - Filter by specific host IDs
  - Filter by last processed timestamp. This property is a bit vague and of little utility. It seems to be the last time the Site Manager system got an update regarding this device.

  ![Get All Devices Example](docs/assets/screenshot_get_all_devices.png)

### ISP Metrics
- **Get** - This endpoint is in **early access**, but I've included it here so you can try it out without reading the UniFi documentation. It might break in the future or have limited usability, etc.

## Functionality

The **Return All** implements pagination. Be careful if you have a lot of endpoints.

## Credentials
This node uses API key authentication to connect to the UniFi Site Manager API.

For detailed instructions, see the [UniFi Site Manager API Getting Started Guide](https://developer.ui.com/site-manager-api/gettingstarted#obtaining-an-api-key).

## Example Workflow
Recommend using the **Split Out** node on the `devices` field to get a better array for processing.

  ![Example workflow](docs/assets/screenshot_example_workflow.png)

  ![Split out devices](docs/assets/screenshot_split_out.png)

## Resources
- [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
- [UniFi Site Manager API Documentation](https://developer.ui.com/site-manager-api/gettingstarted)
- [UniFi Developer Console](https://developer.ui.com/)
- [Installation guide for n8n community nodes](https://docs.n8n.io/integrations/community-nodes/installation/)
npm package: @mspiderv/vuejwtauth
Description: JWT auth library for Vue.js applications
Author: Matej Vitaz
Latest version: 1.2.2

# JSON Web Tokens auth for [Vue.js](https://vuejs.org/) and [Quasar](https://quasar.dev/)

**This is a client-side** [JSON Web Tokens (JWT)](https://jwt.io/) authentication package for [Vue.js](https://vuejs.org/) and [Quasar](https://quasar.dev/) applications.

**This is not a server-side solution.** If you need a server-side JWT auth, then take a look at our Laravel server-side package. - *comming soon*

## Features

 - **Login** functionality.
 - **Remember me** functionality. Stores JWT in *token storage*, using one of the following drivers:
   - `cookie` driver (*recommended*).
   - `localStorage` driver.
   - You can create your own *token storage* driver.
 - **Logout** functionality.
   - Automatically logout idle users (after 5 minutes by default, but you can configure it or fully disable).
 - **Fetch user** functionality (retrieve any extra information about logged user from API).
 - **Automatically refreshes JWT** to make it valid for ever (based on JWT `exp` property).
 - **Decodes JWT** to JSON.
   - Allows you to read information from JWT directly.
   - Uses [jwt-decode](https://github.com/auth0/jwt-decode) under the hood.
   - You can create your own *token decoder* driver.
 - Sends HTTP requests to your JWT auth API, using one of the following drivers:
   - [Axios](https://github.com/axios/axios) HTTP driver.
   - You can create your own *HTTP* driver.
 - Uses [Vuex](https://vuex.vuejs.org/) under the hood, which allows you to use all Vuex module functionality directly.
 - Fully [configurable](docs/configuration.md).

## Contents

1. [Installation](docs/installation.md)
2. [Usage](docs/usage.md)
3. [Protecting routes](docs/protect-routes.md)
4. [Configuration](docs/configuration.md)

## Requirements

1. This package assumes, you use [VueRouter](https://router.vuejs.org/) in your application.
2. JWT auth server. (Do you need a server-side JWT auth solution? Take a look at our Laravel server-side package - *comming soon*)

## Thanks to

These are the main packages we use under the hood.

 - [axios](https://github.com/axios/axios)
 - [voltace/browser-cookies](https://github.com/voltace/browser-cookies)
 - [TehShrike/deepmerge](https://github.com/TehShrike/deepmerge)
 - [EventEmitter2](https://github.com/EventEmitter2/EventEmitter2)
 - [auth0/jwt-decode](https://github.com/auth0/jwt-decode)
npm package: @mspony/gitlab-mcp-server-fix
Description: A patched version of GitLab MCP server with JSON Schema fixes for modern clients
Author: mspony
Latest version: 1.0.3

# GitLab MCP Server (Patched)

A Model Context Protocol (MCP) server for GitLab, patched to fix JSON Schema compatibility issues with modern clients (like Claude Desktop and Cursor).

## Why this fork?

The official `@modelcontextprotocol/server-gitlab` package generates JSON Schemas with `type: ["object"]`, which is rejected by stricter MCP clients. This version includes a middleware layer that recursively fixes these schemas to `type: "object"` and handles other compatibility edge cases.

## Installation

You can use this server directly with `npx` without installing it globally:

```bash
npx @mspony/gitlab-mcp-server-fix
```

## Configuration

Add the following to your MCP client configuration (e.g., `claude_desktop_config.json` or `mcp.json`):

```json
{
  "mcpServers": {
    "gitlab": {
      "command": "npx",
      "args": [
        "-y",
        "@mspony/gitlab-mcp-server-fix"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>",
        "GITLAB_API_URL": "https://gitlab.com/api/v4" 
      }
    }
  }
}
```

*Note: For self-hosted GitLab, update `GITLAB_API_URL` to your instance's API endpoint.*

## Features

- **All original GitLab tools**: create_issue, merge_request, push_files, etc.
- **Schema Fix**: Automatically corrects `type: ["object"]` to `type: "object"`.
- **Nullable Fix**: Converts `["string", "null"]` to `type: "string", nullable: true`.

## License

MIT