open-index/open-npm huggingface dataset:
npm package: @solid/oidc-auth-manager
Description: An OpenID Connect (OIDC) authentication manager (OP, RP and RS) for decentralized peer-to-peer authentication
Author: Dmitri Zagidulin
Latest version: 0.25.2

# OIDC Decentralized Authentication Manager

[![](https://img.shields.io/badge/project-Solid-7C4DFF.svg?style=flat)](https://github.com/solid/solid)
[![NPM Version](https://img.shields.io/npm/v/@solid/oidc-auth-manager.svg?style=flat)](https://www.npmjs.com/package/@solid/oidc-auth-manager)
[![Build Status](https://travis-ci.org/solid/oidc-auth-manager.svg?branch=master)](https://travis-ci.org/solid/oidc-auth-manager)

An OpenID Connect (OIDC) peer node (a combination Identity Provider, Relying
Party, Authorization Server and Resource Server) for decentralized
authentication projects such as [Solid](https://github.com/solid/solid).
npm package: @solid/oidc-op
Description: OpenID Connect Provider
Latest version: 0.12.1

# OpenID Connect for Nodejs

## Deprecation Notice

This repository has been archived, and will no longer be maintained by the
Solid Project.

Active maintenance has been moved to
**[interop-alliance/oidc-op](https://github.com/interop-alliance/oidc-op)**.

## MIT License

[The MIT License](LICENSE.md)

Copyright (c) 2016 [Anvil Research, Inc.](http://anvil.io)
Copyright (c) 2017-2019 The Solid Project
npm package: @solid/oidc-rp
Description: OpenID Connect Relying Party client library
Author: Solid Project
Latest version: 0.12.1

# OpenID Connect Relying Party _(oidc-rp)_

[![](https://img.shields.io/badge/project-Solid-7C4DFF.svg?style=flat-square)](https://github.com/solid/solid)
[![Build Status](https://travis-ci.org/solid/oidc-rp.svg?branch=master&style=flat-square)](https://travis-ci.org/solid/oidc-rp)
[![npm version](https://badge.fury.io/js/%40solid%2Foidc-rp.svg)](https://badge.fury.io/js/%40solid%2Foidc-rp)

> OpenID Connect Relying Party for Node.js and the browser.

## Deprecation Notice

This repository has been archived, and will no longer be maintained by the Solid Project.

Active maintenance has been moved to **[interop-alliance/oidc-rp](https://github.com/interop-alliance/oidc-rp)**.

### Contributors

* Christian Smith [@christiansmith](https://github.com/christiansmith)
* Dmitri Zagidulin [@dmitrizagidulin](https://github.com/dmitrizagidulin)

## MIT License

[The MIT License](LICENSE.md)

Copyright (c) 2016 Anvil Research, Inc.
Copyright (c) 2017-2019 The Solid Project
npm package: @solid/oidc-rs
Description: OpenID Connect Resource Server Authentication for Node.js
Latest version: 0.7.0

# OpenID Connect Resource Server Authentication

OpenID Connect Resource Server Authentication for Node.js

## Features

* [x] OAuth 2.0 Bearer Token Usage (RFC 6750)
* [x] JWT Access Token Validation (Specification pending)
* [x] Issuer discovery (OpenID Connect Discovery)
* [x] Dynamic key rotation (OpenID Connect Core)
* [x] Multiple issuer support
* [x] Scope validation
* [x] Allow and deny access by "iss", "aud", and "sub" claims

## Usage

### Install

```bash
$ npm install @solid/oidc-rs
```

### Require

```
const ResourceServer = require('@solid/oidc-rs')
```

### ResourceServer

ResourceServer maintains a cache of provider metadata and JSON Web Keys for verifying signatures. Provider discovery and acquisition of keys takes place when a JWT access token is decoded. The provider metadata and JWK Set are cached in memory. Therefore no configuration is required.

```
const rs = new ResourceServer()
```

The provider cache can be serialized and persisted, then restored like so:

```
const providers = require('./providers.json')
ResourceServer.from({providers}).then(rs => /* ... */)
```

#### Global server authentication

```javascript
const app = express()
app.use(rs.authenticate(options))
```

#### Route specific configuration

```javascript
app.get('/endpoint', rs.authenticate(options), (req, res, next) => {})
```

### Middleware Options

No configuration is _required_ in order to start using this middleware. All options are optional.

```javascript
rs.authenticate({
  realm: 'user',
  scopes: ['foo', 'bar'],
  allow: {
    issuers: ['https://forge.anvil.io'],
    audience: ['clientid1', 'clientid2'],
    subjects: ['userid1', 'userid2', 'useridn']
  },
  deny: { // probably want to use either allow or deny, but not both
    issuers: ['https://forge.anvil.io'],
    audience: ['clientid1', 'clientid2'],
    subjects: ['userid1', 'userid2', 'useridn']
  },
  handleErrors: false, // defaults to true
  tokenProperty: 'token',
  claimsProperty: 'claims'
})
```

* `realm` – Value of "realm" parameter to use in WWW-Authenticate challenge header.
* `scopes` – Array of scope values required to access this resource.
* `allow` – Object with arrays of allowed issuers, audience and subjects.
* `deny` – Object with arrays of restricted issuers, audience and subjects.
* `handleErrors` – When set to false, error conditions will result in a call to `next()`, passing control to the application's error handling.
* `tokenProperty` – Name of property on `req` to assign decoded JWT object. The property will not be set unless defined.
* `claimsProperty` – name of property on `req` to assign verified JWT claims. Defaults to "claims".

## Running tests

### Nodejs

```bash
$ npm test
```

## MIT License

[The MIT License](LICENSE.md)

Copyright (c) 2016 Anvil Research, Inc.
Copyright (c) 2017-2019 The Solid Project
npm package: @solid/solid-multi-rp-client
Description: OpenID Connect client for multiple Relying Parties for Solid
Author: Dmitri Zagidulin
Latest version: 0.7.2

# solid-multi-rp-client

[![](https://img.shields.io/badge/project-Solid-7C4DFF.svg?style=flat)](https://github.com/solid/solid)
[![NPM Version](https://img.shields.io/npm/v/solid-multi-rp-client.svg?style=flat)](https://npm.im/solid-multi-rp-client)

OpenID Connect (OIDC) client manager for multiple Relying Parties for Solid
npm package: @solid/vocab-lit-common
Description: Bundle of vocabularies that includes the following:

  lit_core: The LIT Core Ontology. The LIT is intended to be a collection of utility libraries to ease the
 adoption of RDF for developers.

  lit_consent: Consent vocabulary defining LIT-specific terms
Author: @inrupt/lit-artifact-generator
Latest version: 0.4.14

ERROR: No README data found!
npm package: @solid/vocab-solid-common
Description: Bundle of vocabularies that includes the following:

  solid-meta-server-creational: The Solid vocabulary providing terms (e.g. classes, properties and text strings (e.g.
 informative labels or error messages) used by Solid servers at server creation time
Author: @inrupt/lit-artifact-generator
Latest version: 0.4.14

ERROR: No README data found!
npm package: @solidbasisventures/intelliwaketsfoundation
Description: NPM package for IntelliWake TypeScript Foundation Components
Author: SolidBasisVentures
Latest version: 5.13.76

# IntelliWakeTSFoundation Reference

This library provides foundational TypeScript utilities for data manipulation, formatting, and validation.

## Core Modules
- DateManager: Comprehensive date/time parsing and formatting.
- SortSearch: Type-safe multi-property sorting.
- Importer: Tabular data analysis and validation (CSV/Excel workflows).
- Formatters: Currency, numeric, and string masking.

## Documentation
- Full Wiki: https://github.com/SolidBasisVentures/IntelliWakeTSFoundation/wiki
- Importer Workflow: See ImporterUsage.md for validation priorities.

## Implementation Patterns
- Always validate imports in this order: Structural (Missing Columns) -> Integrity (Errors) -> Quality (Warnings).
- Use `DateManager` for all date manipulations to ensure cross-timezone consistency.

IntelliwakeTSFoundation, short for the IntelliWake TypeScript Foundation Library provides multiple helper functions that are not present in vanilla JavaScript.

Documentation on how to use these features can be found on our [WIKI](https://github.com/SolidBasisVentures/IntelliWakeTSFoundation/wiki)

This library is meant to be used both on the client side and the server side.

## Date and Date/Time Utilities
The basic premise of the date/time functions is that you can provide any format you like as an input (Javascript Date object, date string (MM/DD/YYYY, YYYY-MM-DD), date/time string, time string, ISO date time string (in a variety of flavors)) and it can parse, manipulate, compare and format them.

## Format Utilities
Sometimes you just need to do some simple manipulation to format things nicely for users, but coming up with the right mechanism use isn't always straight forward.  These utilities provide some great ways to get strings and numbers formatted for common needs.

## Array Utilities
Javascript has an `array.sort()` function.  But, it's implementation is inconsistent (comparison by subtraction for numbers, trying to get strings to sort case-insensitive, comparing dates and/or times, binaries, etc.).  And then, if you want to sort by multiple conditions, the syntax is complicated to the point where it may not be obvious what the intent of the original developer was.

The idea behind this implementation is to handle sorts in a consistent way and vastly simplify the process of stacked sorting.

## Generic Functions
There are a few additional functions that provide other features, like checking additional values for a truthy condition, coalescing 0's and blank strings, and providing a promise based sleep function.
npm package: @solidbasisventures/intelliwaketsnode
Description: NPM package for IntelliWake Node Components
Author: SolidBasisVentures
Latest version: 2.5.3

# IntelliWakeTSFoundation

IntelliwakeTSNode, short for the IntelliWake TypeScript Node Library provides multiple helper functions in a back-end
node server that are not present in vanilla JavaScript.

Documentation on how to use these features can be found on
our [WIKI](https://github.com/SolidBasisVentures/IntelliWakeTSNode/wiki)

## Publishing

Use the following scripts found in the package.json to manage the repository:

To run unit tests:

```
pnpm run Vitest-Watch
```

Note: please update test scripts for any changes.

To run the `consoles.ts` file (with a watch for changes):

```
pnpm run TSNodeDev
```

To update the packages in the package.json:

```
pnpm run Intall-IntelliWake
```

After a significant change, update the minor version number with:

```
pnpm run Verision-Minor-Advance
```

To publish the repository to NPMJS:

```
pnpm run Publish
```
npm package: @solidbasisventures/intelliwaketsreact
Description: NPM package for IntelliWake React Components
Author: SolidBasisVentures
Latest version: 2.2.1

# Configuring NPM Package




## Helpful Resource
This [link](https://blog.logrocket.com/the-complete-guide-to-publishing-a-react-package-to-npm/) explains the basics of using rollup for configuring a react/NPM package. I found the beginning pieces of information here. 



## NPM
The original scope of this assignment was to move the iwaker code into a portable package hosted on NPM repository so that it could be distributed to different projects easily and handed to other developers. As of right now, there is no way that I can find to authenticate command line actions (such as npm install or npm update). Ideally an auth token should be stored in the .npmrc file however the only way this can be used (from what I can see) is to call this using an automated workflow which is not ideal. Another solution pursued was simply pulling the package from GitHub. However this breaks the update (npm update) functionality (see [this](https://medium.com/@jonchurch/use-github-branch-as-dependency-in-package-json-5eb609c81f1a) for more info). There are some other NPM repositories available. 



## Package Components

### Rollup
Rollup is an NPM package that is big used to take the package and complete two tasks: compile the code back down to ES5 so that all browsers can understand it, and “tree-shake” the code so that additional functions that are not used are emitted from the final package”. There are also a few plugins that have been added to rollup.

#### Commands 
In the package.json file, there are two commands that have to do with rollup: build and start. These can be run using the shell command “npm run build” or “npm run start”. The former manually builds the package when run and the latter starts a process that continuously builds the package every time it is saved, which can be very useful. 

### Typescript2 Plugin
This is a simple plugin Rollup which allows for rollup to understand Typescript files. 

### SASS Plugin
This allows for Rollup to understand sass and other files. 

### Bable Plugin
This is not currently added but it might be necessary if any normal javascript files are put in. I am not sure though



## Files & Directories

### rollup.config.js
This is the configuration file for rollup. See [this](https://rollupjs.org/guide/en/#creating-your-first-bundle) for more info. 

### tsconfig,json
This is the configuration file for the typescript plugin. [This](https://www.typescriptlang.org/docs/handbook/compiler-options.html) lists all of the options for this file.

### src
This is the directory where all of the code package code goes.

### dist 
When rollup runs, all of the generated files are dumped in here. It can be very helpful to delete these if many changes are made; otherwise, extra files may continue to be present. 

#### Locally link files

### This App

In terminal, run; npm link

### Consuming App

In terminal, run: npm link @denjpeters/intelliwakereact
npm package: @solidbasisventures/intelliwaketsreact17
Description: NPM package for IntelliWake React 17 Components
Author: SolidBasisVentures
Latest version: 4.1.40

# Configuring NPM Package




## Helpful Resource
This [link](https://blog.logrocket.com/the-complete-guide-to-publishing-a-react-package-to-npm/) explains the basics of using rollup for configuring a react/NPM package. I found the beginning pieces of information here. 



## NPM
The original scope of this assignment was to move the iwaker code into a portable package hosted on NPM repository so that it could be distributed to different projects easily and handed to other developers. As of right now, there is no way that I can find to authenticate command line actions (such as npm install or npm update). Ideally an auth token should be stored in the .npmrc file however the only way this can be used (from what I can see) is to call this using an automated workflow which is not ideal. Another solution pursued was simply pulling the package from GitHub. However this breaks the update (npm update) functionality (see [this](https://medium.com/@jonchurch/use-github-branch-as-dependency-in-package-json-5eb609c81f1a) for more info). There are some other NPM repositories available. 



## Package Components

### Rollup
Rollup is an NPM package that is big used to take the package and complete two tasks: compile the code back down to ES5 so that all browsers can understand it, and “tree-shake” the code so that additional functions that are not used are emitted from the final package”. There are also a few plugins that have been added to rollup.

#### Commands 
In the package.json file, there are two commands that have to do with rollup: build and start. These can be run using the shell command “npm run build” or “npm run start”. The former manually builds the package when run and the latter starts a process that continuously builds the package every time it is saved, which can be very useful. 

### Typescript2 Plugin
This is a simple plugin Rollup which allows for rollup to understand Typescript files. 

### SASS Plugin
This allows for Rollup to understand sass and other files. 

### Bable Plugin
This is not currently added but it might be necessary if any normal javascript files are put in. I am not sure though



## Files & Directories

### rollup.config.js
This is the configuration file for rollup. See [this](https://rollupjs.org/guide/en/#creating-your-first-bundle) for more info. 

### tsconfig,json
This is the configuration file for the typescript plugin. [This](https://www.typescriptlang.org/docs/handbook/compiler-options.html) lists all of the options for this file.

### src
This is the directory where all of the code package code goes.

### dist 
When rollup runs, all of the generated files are dumped in here. It can be very helpful to delete these if many changes are made; otherwise, extra files may continue to be present. 

#### Locally link files

### This App

In terminal, run; npm link

### Consuming App

In terminal, run: npm link @denjpeters/intelliwakereact
npm package: @solidbasisventures/intelliwaketssveltekitv1
Description: ## Overview This NPM package provides common functions and components that enhance a SvelteKit project.
Latest version: 1.9.31

# IntelliWake TS SvelteKit V1

## Overview
This NPM package provides common functions and components that enhance a SvelteKit project.

It leverages other IntelliWake modules.

## Installation
Installing this package can be done with `npm` or `pnpm`
```shell
pnpm install @solidbasisventures/intelliwaketssveltekitv1
```


## Usage

### Styling
For the styling of this package to work, tailwind must be installed on the host project. Then the following line should
be added to `tailwind.config.cjs` in the host project.

`'./node_modules/@solidbasisventures/intelliwaketssveltekitv1/**/*.{svelte,js,ts,jsx,tsx}'`

The end result should look like this:

```javascript
/** @type {import('tailwindcss').Config} */
module.exports = {
    content: [
        './src/**/*.{html,js,svelte,ts}',
        './node_modules/@solidbasisventures/intelliwaketssveltekitv1/**/*.{svelte,js,ts,jsx,tsx}'
    ],
}
```

This will cause tailwind to automatically include the tailwind classes found in this library.

### Importing
All imports are named imports and should look as follows

```javascript
import {ComponentName} from "@solidbasisventures/intelliwaketssveltekitv1"
```
npm package: @solidbasisventures/intelliwaketssveltekitv2
Description: ## Overview This NPM package provides common functions and components that enhance a SvelteKit project.
Latest version: 2.0.81

# IntelliWake TS SvelteKit V2

## Overview
This NPM package provides common functions and components that enhance a SvelteKit project.

It leverages other IntelliWake modules.

## Installation
Installing this package can be done with `npm` or `pnpm`
```shell
pnpm install @solidbasisventures/intelliwaketssveltekitv2
```


## Usage

### Styling
For the styling of this package to work, tailwind must be installed on the host project. Then the following line should
be added to `tailwind.config.cjs` in the host project.

`'./node_modules/@solidbasisventures/intelliwaketssveltekitv1/**/*.{svelte,js,ts,jsx,tsx}'`

The end result should look like this:

```javascript
/** @type {import('tailwindcss').Config} */
module.exports = {
    content: [
        './src/**/*.{html,js,svelte,ts}',
        './node_modules/@solidbasisventures/intelliwaketssveltekitv1/**/*.{svelte,js,ts,jsx,tsx}'
    ],
}
```

This will cause tailwind to automatically include the tailwind classes found in this library.

### Importing
All imports are named imports and should look as follows

```javascript
import {ComponentName} from "@solidbasisventures/intelliwaketssveltekitv1"
```
npm package: @solidblock/react-filemanager
Description: A react based file manager plugin.
Author: andy-j-phillips
Latest version: 0.0.19


<h1 align="center">React Filemanager</h1>

<div align="center">

[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/andy-j-phillips/react-filemanager/blob/HEAD/LICENSE)
[![npm latest package](https://img.shields.io/npm/v/@solidblock/react-filemanager/latest.svg)](https://www.npmjs.com/package/@solidblock/react-filemanager)
[![npm downloads](https://img.shields.io/npm/dm/@solidblock/react-filemanager.svg)](https://www.npmjs.com/package/@solidblock/react-filemanager)
[![GitHub branch status](https://img.shields.io/github/checks-status/andy-j-phillips/react-filemanager/HEAD)](https://github.com/andy-j-phillips/react-filemanager/commits/HEAD/)

</div>

### About

A react based file manager plugin.

Full documentation can be found [here](https://andy-j-phillips.github.io/react-filemanager/).

### Installation

For installation you can use the following:-

`npm i @solidblock/react-filemanager`

or

`yarn add @solidblock/react-filemanager`