open-index/open-npm huggingface dataset:
npm package: @krisbyte/nymc
Description: A npm/yarn malware scanner
Author: krisbyte
Latest version: 0.2.2

# nymc

A CLI tool that scans your Node.js project for known malware packages. It checks your project's `package.json`, lock files, `node_modules`, and the full dependency tree against a configurable list of known malicious packages.

## Installation

```bash
npm install @krisbyte/nymc
```

## Usage

### Initialize configuration

```bash
nymc --init
```

This creates a `.nymc/config.json` file in your project root. Add known malware packages to the `packages` array using the `name@version` format:

```json
{
  "version": "0.0.1",
  "url": "",
  "httpsHeader": "",
  "packages": [
    "malicious-pkg@1.0.0",
    "@scope/bad-pkg@2.3.1"
  ]
}
```

### Run the scan

```bash
nymc
```

### Fetch packages from a remote URL

Instead of maintaining a local `packages` list, you can fetch it from a remote endpoint. Set the `url` field in `.nymc/config.json` to point to a JSON API that returns an array of package strings:

```json
{
  "url": "https://example.com/malware-list.json",
  "httpsHeader": "Authorization: Bearer <token>"
}
```

- **`url`** – The endpoint that returns a JSON array of `name@version` strings.
- **`httpsHeader`** – *(Optional)* A single HTTP header to include with the request, formatted as `"Header-Name: value"`. Useful for authenticated endpoints.

Then run the scan with the `--network` flag:

```bash
nymc --network
```

When `--network` is used, the remote package list takes precedence over the local `packages` array.

## How it works

For each package in the configuration, nymc runs four checks:

1. **package.json** - Checks if the package is listed in `dependencies` or `devDependencies`
2. **Lock file** - Checks `package-lock.json` (npm) or `yarn.lock` (yarn) for the package
3. **node_modules** - Checks if the package is physically installed with the matching version
4. **Dependency tree** - Runs `npm ls --all` or `yarn list --depth=Infinity` to find the package in nested dependencies

If any malware is detected, all checks still run to give a complete report before exiting with code 1.

## License

MIT
npm package: @kriscarilloxyz/hiboutik-js
Description: hiboutik-js is a client for https://username.hiboutik.js
Author: kriscarilloxyz
Latest version: 0.10.1

# hiboutik-js

hiboutik-js is a client for https://username.hiboutik.js

## Installation

Use the package manager [npm](https://www.npmjs.com/) to install hiboutik-js.

```bash
npm i @kriscarilloxyz/hiboutik-js
```

## Usage

```javascript
const Hiboutik = require('@kriscarilloxyz/hiboutik-js')

const client = new Hiboutik(host, username, password) 
const productsList = await client.productsList()
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)`
npm package: @kriscarilloxyz/nethunt-js
Description: nethunt-js is a wrapper for Nethunt API written in node-js.
Author: kriscarilloxyz
Latest version: 1.0.0

# nethunt-js

nethunt-js is a wrapper for https://nethunt.com/integration-api

<!-- badges: start -->

[![Inline docs](http://inch-ci.org/github/montpcdev/nethunt-js.svg?branch=master)](http://inch-ci.org/github/montpcdev/nethunt-js)
[![Known Vulnerabilities](https://snyk.io/test/github/montpcdev/nethunt-js/badge.svg?targetFile=package.json)](https://snyk.io/test/github/montpcdev/nethunt-js?targetFile=package.json)
[![Codecov test coverage](https://codecov.io/github/montpcdev/nethunt-js/coverage.svg?branch=master)](https://codecov.io/github/Rdatatable/data.table?branch=master)
[![JavaScript Style Guide: Good Parts](https://img.shields.io/badge/code%20style-goodparts-brightgreen.svg?style=flat)](https://github.com/montpcdev/nethunt-js "JavaScript The Good Parts")
[![HitCount](http://hits.dwyl.com/montpcdev/netunt-js.svg)](http://hits.dwyl.com/montpcdev/netunt-js)
[![https://nodei.co/npm/@kriscarilloxyz/nethunt-js.png?downloads=true&downloadRank=true&stars=true](https://nodei.co/npm/@kriscarilloxyz/nethunt-js.png?downloads=true&downloadRank=true&stars=true)](https://www.npmjs.com/package/@kriscarilloxyz/nethunt-js)

<!-- badges: end -->

## Installation

Use the package manager [npm](https://www.npmjs.com/) to install nethunt-js.

```bash
npm i @kriscarilloxyz/nethunt-js
```

## Usage

```javascript
const Nethunt = require('@kriscarilloxyz/nethunt-js')

const client = new Nethunt(username, password) 
const readableFolders = await client.readableFolders()
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License

[MIT](https://choosealicense.com/licenses/mit/)
npm package: @kriscarilloxyz/ringover-js
Description: Ringover client for node.js
Author: kriscarilloxyz
Latest version: 0.2.0

# ringover-js

ringover-js is a client for https://developer.ringover.com.

## Installation

Use the package manager [npm](https://www.npmjs.com/) to install ringover-js.

```bash
npm i @kriscarilloxyz/ringover-js
```

## Usage

```javascript
const Ringover = require('@kriscarilloxyz/ringover-js')

const client = new Ringover(token) 
const callsList = await client.callsList(params)
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @krisdages/aurelia-store
Description: Aurelia single state store based on RxJS
Author: Vildan Softic
Latest version: 1.7.0-rxjs-peer.0

# @krisdages/aurelia-store

This is an unsupported fork of [aurelia-store](https://github.com/aurelia/store) that supports RXJS 6 or 7 by 
making `rxjs` a peer dependency. Depending on your version of npm, you may need to add `rxjs` to your package.json
if it is not there already.

# aurelia-store

This library is part of the [Aurelia](http://www.aurelia.io/) platform and contains a plugin that provides a single state store based on RxJS.
Various examples can be found in the [samples repository](https://github.com/zewa666/aurelia-store-examples)..

You can find complete documentation on setup and usage in the official [Aurelia Developer Hub](https://aurelia.io/docs/plugins/store)

> To keep up to date on [Aurelia](http://www.aurelia.io/), please visit and subscribe to [the official blog](http://blog.aurelia.io/) and [our email list](http://eepurl.com/ces50j). We also invite you to [follow us on twitter](https://twitter.com/aureliaeffect). If you have questions look around our [Discourse forums](https://discourse.aurelia.io/), chat in our [community on Gitter](https://gitter.im/aurelia/discuss) or use [stack overflow](http://stackoverflow.com/search?q=aurelia). Documentation can be found [in our developer hub](http://aurelia.io/docs). If you would like to have deeper insight into our development process, please install the [ZenHub](https://zenhub.io) Chrome or Firefox Extension and visit any of our repository's boards.

## Dependencies

* [RxJS v6](https://github.com/ReactiveX/rxjs)
* aurelia-dependency-injection
* aurelia-templating
* aurelia-logging
* aurelia-pal

## Polyfills

* Object.entries ([MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/entries#Polyfill))

## Platform Support

This library can be used in the **browser** and **node**.

## Building The Code

To build the code, follow these steps.

1. Ensure that [NodeJS](http://nodejs.org/) is installed. This provides the platform on which the build tooling runs.
2. From the project folder, execute the following command:

  ```shell
  npm install
  ```
3. To build the code, you can now run:

  ```shell
  npm run build
  ```
4. You will find the compiled code in the `dist` folder, available in various module formats.

> In order to build for a single target, run `-- --format <<target>>`, picking the desired target such as ES2015, AMD and so on. 

## Running The Tests

To run the unit tests, first ensure that you have followed the steps above in order to install all dependencies and successfully build the library. Once you have done that, proceed with these additional steps:

1. For single execution run:

  ```shell
  npm run test
  ```
2. For continuous tdd style:

  ```shell
  npm run test-watch
  ```
3. You can find the coverage report built after each test run:

  ```shell
  cat /test/coverage-jest/index.html
  ```
npm package: @krisdages/custom-multi-keytar
Description: Prepackaged multiplatform keytar for multiple versions of Node and Electron
Latest version: 7.2.0

# Prepackaged multiplatform `keytar` for multiple versions of Node and Electron

* keytar Repo: https://github.com/atom/node-keytar
* keytar Homepage: http://atom.github.io/node-keytar,

This is a wrapper for the `keytar` Native Module that includes the prebuilt binaries for several Node and Electron platforms/architectures
and loads the corresponding implementation for the current runtime, platform, and architecture.

I created this to avoid having to build multiple versions of my Electron project's asar file when `keytar` was the only native dependency.

This is not officially supported, and the preinstalled versions of keytar are limited to those needed for my project.
They are likely to change in the future.
If you want to use this, I'd recommend forking and modifying the versions/platforms in `lib/versions.js`   

## Installing

```sh
npm install @krisdages/custom-multi-keytar
#or
npm install keytar@npm:@krisdages/custom-multi-keytar
```

## Building

  * Clone the repository
  * Run `npm install`
  * Run `npm run build` to download the configured prebuilt binaries.

## Supported versions

###Electron:
* 3.x (for a little while longer), 10.x, 11.x

###Node:
* 10.x, 12.x

###Platforms / Architectures
* `darwin-x64`, `linux-x64, `win32-x64`
npm package: @krisdages/electron-process-manager
Description: Process manager UI for Electron applications - Fork with support for @electron/remote
Latest version: 3.0.0

# Process Manager UI for Electron Apps

## Fork using @electron/remote instead of builtin remote module
* Minimum electron version is `10`
* [@electron/remote](https://github.com/electron/remote) is a peerDependency. It needs to be initialized in the main process. Follow the instructions in the link.

## Original 1.0 Readme

This package provides a process manager UI for Electron applications.

It opens a window displaying a table of every processes run by the Electron application with information (type, URL for `webContents`, memory..).

[![npm version](https://badge.fury.io/js/electron-process-manager.svg)](https://badge.fury.io/js/electron-process-manager)

![screenshot](https://github.com/getstation/electron-process-manager/raw/master/.github/screenshots/window.png)

~~:warning: For `@electron>=3.0.0, <7.x`, use version `0.7.1` of this package.
For versions `>=7.x`, use latest.~~

It can be useful to debug performance of an app with several `webview`.

It's inspired from Chrome's task manager.

## Features

- [ ] Memory reporting
- [ ] Link memory data to web-contents (for electron >=1.7.1)
- [x] Kill a process from the UI
- [x] Open developer tools for a given process
- [x] CPU metrics
- [x] Sort by columns

⚠️ Unfortunately, memory info are no longer available in Electron>=4 (see [electron/electron#16179](https://github.com/electron/electron/issues/16179))

## Installation

```bash
$ npm install electron-process-manager
```

## Usage
```js
const { openProcessManager } = require('electron-process-manager');

openProcessManager();
```

## Options
`openProcessManager` function can take options in paramters

#### options.defaultSorting
**defaultSorting.how**: `'ascending' | 'descending'`

**defaultSorting.path**:

| Field name         | path                       |
|--------------------|----------------------------|
| Pid                | 'pid'                      |
| WebContents Domain | 'webContents.0.URLDomain'  |
| Process Type       | 'webContents.0.type'       |
| Private Memory     | 'memory.privateBytes'      |
| Shared Memory      | 'memory.sharedBytes'       |
| Working Set Size   | 'memory.workingSetSize'    |
| % CPU              | 'cpu.percentCPUUsage'      |
| Idle Wake Ups /s   | 'cpu.idleWakeupsPerSecond' |
| WebContents Id     | 'webContents.0.id'         |
| WebContents Type   | 'webContents.0.type'       |
| WebContents URL    | 'webContents.0.URL'        |

example:
```js
const { openProcessManager } = require('electron-process-manager');

openProcessManager({ how: 'descending', path: 'cpu.percentCPUUsage' });
```

## Future

- Add physical memory (noted as "Memory" in Chrome's task manager)
- Add networks metrics

Pull requests welcome :)

## License

MIT License
npm package: @krisdages/electron-process-reporter
Description: Utility to extract interesting process reports of an Electron application.
Latest version: 2.0.0-rxjs7-1.4.0

# electron-process-reporter
Utility to extract interesting process reports of an Electron application.

## Installation 
```bash
$ npm install --save electron-process-reporter
```

## Usage

### onExtendedProcessMetrics
Returns an Rx.Observable that emits reports of `ExtendedProcessMetric` every `options.samplingInterval` ms.
```js
import { app } from 'electron';
import { onExtendedProcessMetrics } from 'electron-process-reporter';

onExtendedProcessMetrics(app, { samplingInterval: 1000 }) // returns a rx.Observable
  .subscribe(report => console.log(report))
```

### onExcessiveCPUUsage
Will emit `ExtendedProcessMetric[]` when a process exceeds the `options.percentCPUUsageThreshold` on more than `options.samplesCount` samples.
```js
import { app } from 'electron';
import { onExcessiveCPUUsage } from 'electron-process-reporter';

onExcessiveCPUUsage(
  app,
  {
    samplesCount: 1,
    percentCPUUsageThreshold: 90,
  }) // returns a rx.Observable
  .subscribe(report => console.log(report))
```

### onProcessTreeMetricsForPid
Returns an Rx.Observable that emits `PidUsage[]` every `options.samplingInterval` ms.
```js
import { onProcessTreeMetricsForPid } from 'electron-process-reporter';

onProcessTreeMetricsForPid(process.pid, { samplingInterval: 1000 }) // returns a rx.Observable
  .subscribe(report => console.log(report))
```

### onExcessiveCPUUsageInProcessTree
Will emit `PidUsage[]` when a process of the tree exceeds the `options.percentCPUUsageThreshold` on more than `options.samplesCount` samples.
```js
import { onExcessiveCPUUsageInProcessTree } from 'electron-process-reporter';

onExcessiveCPUUsageInProcessTree(
  process.pid, // in the main process
  {
    samplesCount: 1,
    percentCPUUsageThreshold: 90,
  }) // returns a rx.Observable
  .subscribe(report => console.log(report))
```