open-index/open-npm huggingface dataset:
npm package: @mariachibear/cutting-ninja-cli
Description: Cutting Ninja CLI permitting to short URL's by copying them
Author: Rubén Conde
Latest version: 0.1.2

# Cutting Ninja CLI [![npm version](https://badge.fury.io/js/@mariachibear%2Fcutting-ninja-cli.svg)](https://badge.fury.io/js/@mariachibear%2Fcutting-ninja-cli)

Command line tool for shorting URL's as you copy them. Using [Cutting Ninja](https://nnjct.pw/Jqq) as URL shortener and [PM2](https://nnjct.pw/jHk) as base for monitoring constantly.

## Prerequisites

1. [Node.js](https://nnjct.pw/jgE) and [npm](https://nnjct.pw/kS5) installed.

## Installation

```shell
npm install @mariachibear/cutting-ninja-cli --location=global
```

## Usage

At the moment of the package install you can start copying URLs and they will be automatically shortened and added to your clipboard. This way you should just `Ctrl+C` and `Ctrl+V`.

### Log In

By default, user-less URLs will be unavailable after some time, so you can log in to save the future shortened URLs as yours:

```shell
nnjct login -e your@email.com -p yourpassword
```

**_You will need to have an already registered account at Cutting Ninja_**

Also, once you have logged in, you can get your user information with :

```shell
nnjct login -i
```

You can always log out with

```shell
nnjct logout
```

### Listener Management

You can initialize, stop and get information from the listener with those commands. This is useful when you don't need short URLs for a while.

```shell
nnjct init

nnjct stop

nnjct info
```

### Enabling on startup

As PM2 is used for maintaining the listener alive, it is possible to configure the listener to be started when entering the operating system. TThose commands will show you what to run to achieve it _(No compatible with Windows for the moment)_.

```shell
nnjct enable

nnjct disable
```

## Additional information

For detailed information you can always execute `nnjct -h` to get all the possible commands.

```shell
Usage: nnjct [options] [command]

Cutting Ninja CLI to short your URL's as you copy them

Options:
  -V, --version    output the version number
  -h, --help       display help for command

Commands:
  login [options]  Login into the system to save the generated URL's as yours
  logout           Logout from the system to save the generated URL's as yours
  init             Start the listener to short your URL's
  info             Get information about the listener that short your URL's
  stop             Stop the listener that short your URL's
  enable           Show configuration to enable the listener on system startup
  disable          Show configuration to disable the listener from system startup
  help [command]   display help for command
```
npm package: @marialenap/my-modal
Description: Test publication package NPM. Contenu créé à partir du tutoriel du site https://www.cril.univ-artois.fr/~boussemart/react/chapter02.html
Author: Maria-Lena PIETRI
Latest version: 1.0.7

# Test de publication de package NPM

Contenu du code créé à partir du tutoriel du site de Frédéric Boussemart -
Maître de conférences en informatique
Tutoriel sur les modales
https://www.cril.univ-artois.fr/~boussemart/react/chapter02.html
npm package: @mariamaneva/js-playground
Description: A simple framework for testing js code snippets
Author: Maria Maneva
Latest version: 0.9.16

# Description

![JS Playground](https://raw.githubusercontent.com/mariamaneva/js-playground-package/main/demo.png)

This is a simple JS/TS code playground framework that I created in order to test code snippets, play Advent of Code, etc a while ago. As my original project got larger, I decided to encapsulate the code-running logic in a package.

All the playground files are listed in a clickable sidebar explorer. Nesting is possible too. To test the output you can use both the DOM and Devtools console.

You can see the updated output after each save as well.

<br/>
<br/>

# Usage

<br/>

1. Install the package

```
npm install @mariamaneva/js-playground
```

2. In your root package.json file, add the following script commands:

```
"scripts": {
  // add these lines
  "start": "npm run start --prefix node_modules/@mariamaneva/js-playground",
  "new-page": "npm run new-page --prefix node_modules/@mariamaneva/js-playground",
  "update-nav": "npm run update-nav --prefix node_modules/@mariamaneva/js-playground",
  "help": "npm run help --prefix node_modules/@mariamaneva/js-playground"
}
```

3. Create a new playground page:

```
npm run new-page --path <your_page_name>.js
```

OR

```
npm run new-page --path <your_page_name>.ts
```

4. Start the project

```
npm start
```

5.  Open **`<your_page_name>.js`** file from the **`sections`** folder and add your code where the `// code` comment is. As you keep updating and saving you can monitor your output in the respective page within the browser.

<br/>
<br/>


### Adding a new page
<br/>

Repeat **step 3** and re-run the project every time you need a new playground file.

<br/>


### Updating the sidebar explorer
<br/>

If you deleted any files from the sections folder, run **`npm run update-nav`** and re-start the project to update the sidebar explorer
npm package: @mariana-tek/anemone
Description: Mariana Tek Embedded Apps SDK
Author: Mariana Tek
Latest version: 1.0.0

# Mariana Anemone
An SDK for building Embedded Apps with Mariana Tek.

## Installation

```npm install @mariana-tek/anemone```

## Documentation

Full reference: https://marianatek.com/developers/guides/mariana-anemone

## Running tests

```npm test```

## Running the example app
**Note:** This example application will only function when loaded within a sandbox for the Mariana Tek Admin Application where a this test Embedded App is installed. If you 
have an idea for a new Embedded App and don't have a sandbox or a test Embedded App installed yet, contact <partners@marianatek.com>.

1. Go to the root of the example app and install dependencies:
```
cd example
npm install
```

2. Update the value of `config` in example/src/utils.js with the correct values for your app:
```js
const config = {
    appId: "{MARIANA_APP_ID}", // the app ID configured for your app
    clientId: "{MARIANA_CLIENT_ID}", // the sandbox client ID for your app
    baseUrl: "{APP_URL}", // when running this locally, this should be http://localhost:1234
};
```

3. Spin up the application:
```
npm start
```
npm package: @marianarocha/zephyr-scale-mcp
Description: Internal MCP server for Zephyr Scale test management (Cloud & Data Center)
Author: AB InBev Growth Tech
Latest version: 0.2.3

Internal Zephyr Scale MCP Server
================================

This is an internal forked MCP server for Zephyr Scale (Jira Cloud & Data Center) used by the BCS platform. It provides tools for test case management, test runs, and folder operations with robust, ID-based folder filtering and is now published as the npm package `@marianarocha/zephyr-scale-mcp`.

Key differences vs upstream:
- Published as a lightweight npm package that can be executed via `npx` (no need to bundle the source inside consumers)
- Folder utilities with exact folder matching by folder ID
- include_subfolders flag for folder queries

Build
-----
- npm install
- npm run build

Publish
-------
Use the following steps to build and publish a new version to npm (requires access to the `@marianarocha` scope):

```
npm login
npm version <patch|minor|major>
npm run build
npm publish --access public
```

Run
---
- `npx -y @marianarocha/zephyr-scale-mcp` (stdio transport)
- or `node build/index.js` when running from a cloned repository

Environment
-----------
- ZEPHYR_BASE_URL (required)
- ZEPHYR_API_KEY (required)
- Optional advanced tuning:
  - `ZEPHYR_METADATA_CACHE_TTL_MS` – cache TTL for status/priority catalogs (default 5 minutes)
  - `ZEPHYR_AUTOMATED_STATUS_KEYWORDS` – comma-separated keywords that should count as automated (default: `automated,automation in progress,automatizado,em automação`)
  - `ZEPHYR_MANUAL_STATUS_KEYWORDS` – comma-separated keywords that should count as manual (default keeps legacy values such as `manual,deploy,aprovado,rascunho`)

Metadata-driven automation
--------------------------
- The MCP now loads Zephyr status/priority catalogs at runtime and exposes them as resources:
  - `zephyr://metadata/statuses`
  - `zephyr://metadata/priorities`
  - `zephyr://metadata/automation_rules`
- `get_test_case` and `search_test_cases_by_folder` responses are enriched with:
  - `statusName`, `priorityName`, and `automationLabel`
  - `automationSummary` aggregates identical to the previous Python-side enhancement
- Python consumers no longer need `ZephyrStatusMappingUseCase`; automation logic lives inside the MCP so downstream services can just forward the enriched payloads.