open-index/open-npm huggingface dataset:
npm package: @giorgosavgeris/passport-zoom-oauth2
Description: Passport Strategy for Zoom OAuth 2.0
Author: Giorgos Avgeris
Latest version: 1.2.0

A simple [Passport](http://passportjs.org/) strategy for Zoom OAuth2.

## Install

npm install @giorgosavgeris/passport-zoom-oauth2

## Usage

### Register the strategy

```javascript
var ZoomStrategy = require('@giorgosavgeris/passport-zoom-oauth2').Strategy;

passport.use(new ZoomStrategy({
    clientID: ZOOM_CLIENT_ID,
    clientSecret: ZOOM_CLIENT_SECRET,
    callbackURL: 'https://www.example.net/oauth/zoom/callback'
  },
  function(accessToken, refreshToken, profile, done) {
    User.findOrCreate(..., function (err, user) {
      done(err, user);
    });
  }
));
```

### Authenticate requests

```javascript
app.get('/auth/zoom', passport.authenticate('zoom', { state: 'pass_state_here' }));

app.get(
  '/auth/zoom/callback',
  passport.authenticate('zoom', { failureRedirect: '/login' }),
  function(req, res) {
    // Successful authentication
    res.redirect('/');
  }
);
```

## License

This project is licensed under the MIT license. See the [LICENSE](LICENSE) file for more info.
npm package: @gios/alerts
Description: This project was generated with [angular-cli](https://github.com/angular/angular-cli) version 1.0.0-beta.22-1.
Latest version: 0.0.1

# AssuranceAlerts

This project was generated with [angular-cli](https://github.com/angular/angular-cli) version 1.0.0-beta.22-1.

## Development server
Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive/pipe/service/class`.

## Build

Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.

## Running unit tests

Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
Before running the tests make sure you are serving the app via `ng serve`.

## Deploying to Github Pages

Run `ng github-pages:deploy` to deploy to Github Pages.

## Further help

To get more help on the `angular-cli` use `ng --help` or go check out the [Angular-CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @giosg-design-system/foundations
Description: Basic style sheet for Giosg Design System. Contains only the most basic styles and variables.
Latest version: 1.1.0

## Intro

Before you start the best thing you could do is to read the foundations package [overview](https://design-system.giosg.app/?path=/docs/foundations-overview--docs) in Storybook to familiarize yourself with the package and the main key points.

### 🔄 How to update existing tokens

#### Figma design tokens are automatically synced with this [github repository](https://github.com/M-Castellarnau/DesignTokens/tree/master).

1. Create a new branch
2. Copy updated `tokens.json` file and replace existing one in this project
3. Run `pnpm build` - that will trigger the script to split tokens into light and dark themes and generate `index.css` with updated variables
4. Verify output and update storybook components if needed
5. Update tests/screenshots if needed
6. Commit your changes if you are fine with them
7. Read the general rules on how to create changesets in [publishing settings](/README.md#Publishing)

### ⁉️ Resolving-Referencing -ref- tokens.

In the design-system we have two levels of nesting in `tokens.json` `ref` and `sys`. Reference level tokens are just building blocks to compose system level tokens. **They should not be used by users directly**.

In automation scripts we resolve the end value of sys tokens and remove ref tokens from the final output.

- Resolving and filtering ref tokens. ( Currently enabled )
![filtering refs](./assets/filter-refs.png)

- Keeping and referencing ref tokens.
  ![keeping refs](./assets/keep-refs.png)
npm package: @giosg-design-system/icons
Description: svg based react icon components
Latest version: 1.3.7

## Contribution guide

We welcome contributions from everyone. Here are a few ways you can help.

## Intro

Before you start the best thing you could do is to read the icon's package [overview](https://design-system.giosg.app/?path=/docs/icons-overview--docs) in Storybook to familiarize yourself with the package and the main key points.

### ➕ How to add a new icon

1. **Create a new branch.**
2. **Obtain the icon SVG:**
   - Get the icon from a designer or pick one from the Figma design system.
   - Icons must follow official design guidelines (e.g., 24px height).
3. **Format the SVG code:**
   Open the SVG in a code editor and ensure it follows this structure:

   - **Root `<svg>`:** Must have `fill="none"`, `height="24"`, and a `viewBox="0 0 24 24"`.
   - **Main Path:** Must have `id="main"` and `fill="#2A293A"`.
   - **Grouping:** If the icon has multiple `<path>` elements, they should be wrapped in a `<g>` tag.
   - **Secondary Paths:** You may use `id="alt"` or `id="accent"` for other parts of the icon.

   **Example of a correct SVG:**

   ```xml
   <svg width="24" height="24" viewBox="0 0 24 24" fill="none" ...>
     <!-- For a single path icon -->
     <path id="main" fill="#2A293A" d="..." />

     <!-- If multiple paths are needed, wrap them in a <g> -->
     <g id="main" fill="#2A293A">
       <path d="..." />
       <path d="..." />
     </g>
   </svg>
   ```

   _Tip: Always compare your SVG structure with existing ones in `./src/svg/`._

4. **Add the file:**
   - Put the SVG file into `./src/svg/`.
5. **Generate components:**
   - Run `pnpm svg` inside the icons package (~packages/icons). This triggers the pipeline to convert SVGs into React components.
6. **Verify and Update:**

   - Update tests and screenshots if necessary.

   To update a screenshot, you can use the `test-docker` command. This will run the Playwright tests in a Docker container and update the screenshot if needed.
   To update the screenshot manually, download the test results from the Playwright report in the PR comment and copy the `picture-actual` file from the `playwright_screenshots/test-results` folder to the `storybook/__screenshots__` folder one by one and replace the existing file.

7. **Submit:**
   - Commit your changes and open a pull request.
   - Follow the [publishing settings](/README.md#Publishing) for creating changesets.
npm package: @giosg/datasources
Description: Classes for accessing resources of giosg systems.
Author: giosg
Latest version: 2.0.1

# giosg datasources

This is a collection of resource datasources used to access and modify giosg resources.

# How to use

`npm install @giosg/datasources`

```javascript
import Datasources from '@giosg/datasources';

const datasources = new Datasources(
    authorizationHeader,
    reportingServiceOrigin, // Optional
    interactionDesignerOrigin, // Optional
    realtimeSdk // Optional. Required for streaming. Has to be pre-connected!
);
```

<span style="color:red"> After adding new datasource you need to `npm install` and reload vscode to get rid of errors!</span>

## Publishing

<span style="color:red">Before publishing, remember to consider the effects your changes have for our users.</span> See [semantic versioning](https://semver.org/).

For publishing, you need access to giosg organization in npm. You can request that from one of the organization admins or request them to publish the package.

1. Update CHANGELOG.md, run `npm version <patch|minor|major>` and `npm run prepare`, and commit.
2. Create pull request.
3. Request a review from another experienced developer.
4. Merge the pull request after approval and passed tests.
5. Pull master locally.
6. Login to npm with `npm login --scope=giosg`. You will be prompted for credentials.
7. Publish the package with: `npm publish --access public`. `--access public` flag is mandatory because organization packages default to `restricted`.

# Changelog

Remember to maintain changelog:
See: `CHANGELOG.md`
npm package: @giosg/pub-sdk
Description: TypeScript interfaces for Giosg Pub
Author: Giosg
Latest version: 2.1.5

# Giosg Pub SDK and interfaces

## This folder should contain some kind of ts interfaces

## Publishing

<span style="color:red">Before publishing, remember to consider the effects your changes have for our users.</span> See [semantic versioning](https://semver.org/).

Script `npm run prepare` will run before publishing automatically.
Make sure you are in the `giosg_pub/interfaces` folder when you are trying to publish the package. Don`t publish something else by accident. If you did, unpublish it within 72 hours.
For publishing, you need access to giosg organization in npm. You can request that from one of the organization admins or request them to publish the package.

1. Update CHANGELOG.md, update package version (e.g. with `npm --no-git-tag-version version <major|minor|patch>`), and commit.
2. Create pull request.
3. Request a review from another experienced developer.
4. Merge the pull request after approval and passed tests.
5. Pull master locally.
6. Login to npm with `npm login --scope=giosg`. You will be prompted for credentials.
7. Build version with `npm run prepare` command.
8. Publish the package with: `npm publish --access public`. `--access public` flag is mandatory because organization packages default to `restricted`.
9. Create a new tag on the latest commit on master branch `git tag vX.Y.Z` `X.Y.Z` being the published version.
10. Push the tag to remote `git push --tags`.

## TODO:

- add lint
- add grammarchek
npm package: @giosg/types
Description: TypeScript interfaces for GiosgAPI
Author: Giosg
Latest version: 12.1.7

# giosg types

This is a collection of interfaces used in giosg services.

# How to use

`npm install @giosg/types`

# Development and publishing

See: `static/common-interfaces/DEVELOPMENT.md`

# Changelog

Remember to maintain change log:
See: `static/common-interfaces/CHANGELOG.md`
npm package: @giosg/ui-components
Description: [![Build Status](https://dronev1.int.giosg.com/api/badges/giosg/ui-components/status.svg)](https://dronev1.int.giosg.com/giosg/ui-components)
Author: giosg
Latest version: 24.0.0

# giosg UI components

[![Build Status](https://dronev1.int.giosg.com/api/badges/giosg/ui-components/status.svg)](https://dronev1.int.giosg.com/giosg/ui-components)

This is a collection of generic Web user interface components used in giosg services.

# Developing

See [DEVELOPMENT.md](DEVELOPMENT.md) for instructions.

# How to use

`npm install @giosg/ui-components`

Wrap whole application into `<Root>` component (this component add global styling into page).

If you do not want to change body styling, then wrap your application into `<RootWrapper>` component instead of `<Root>`.

See [demo page](https://ui-components.int.giosg.com) for usage examples.

See peerDependencies for additional mandatory dependencies. If you need to support IE11, you have to provide polyfills for Symbol, Map, and Set.

# Theming

You can define your own theme using `index.Theme` interface and take it into use with `setTheme` function.

```javascript
import { setTheme } from "@giosg/ui-components/src/theme/theme";
setTheme(theme);
```

Just be sure to call it before importing anything else from `@giosg/ui-components`. Otherwise, you have to forcefully rerender already rendered components after applying the theme!

Currently active theme can be read from `index.theme`, and the default theme can be read with `index.getDefaultTheme()`.

Theming support is at very early stage and contains only colors (18.7.2019).

# styled-components

Component styles are defined using [styled-components](https://www.styled-components.com/docs/basics) npm package and [emotion](https://emotion.sh/docs/introduction)
npm package: @giovanebribeiro/taglog
Description: A tool to generate git tags with messages based on git commits since last tag (changelog)
Author: Giovane Boaviagem
Latest version: 0.1.2

# taglog

![npm](https://img.shields.io/npm/v/@giovanebribeiro/taglog.svg)

A tool to generate git tags with messages based on git commits since last tag

## Installation

`$ npm install --save-dev @giovanebribeiro/taglog`

## Configuration and usage

The recommended usage for this package is with [npm-version](https://docs.npmjs.com/cli/version) with `--no-git-tag-version` flag,
because our goal is replace the git tag creation of npm-version and use ours. To do so, we add some configurations in package.json 
file:

```json

{
 ...
 "taglog": {
    "lineFormat": "* %h %s                       // the line format for 'git-log --pretty'. This is the default option",
    "tagPrefix": "v                              // the tag prefix. This is the default option.",
    "tagTitle": "Custom release version title %s // some custom title for the tag message. '%s' is replaced by the new tag name. The default option is: 'Release version <new_tag_name>'"
  },
  "scripts": {
    "build": "npm version --no-git-tag-version ",
    "version": "git commit -am \"build: release version\" && taglog $npm_package_version",
    "postversion": "git push --follow-tags"
  },
}
  
```

And, to bump the version, create the tag and push, use: `npm run build -- patch|minor|major`

As final result, the git log message will have all the commits between previous tag and actual tag:

```
$ git for-each-ref --sort=-taggerdate --count=1 --format '%(refname) (%(taggerdate))\n===\n\n%(subject)\n\n%(body)' refs/tags
refs/tags/v0.1.0 (Thu Sep 12 14:22:10 2019 -0300)
===

Release version 0.1.0

build: release version
refactor: improvements to better readability
feat: add commit parser support
package.json update without pattern
build: package.json adjustments and package-cleaning
build: adjustments on commit preset
feat: add conventionalChangelog support
build: release version

$ 
```

To other infos: `taglog --help`
npm package: @giovani.queimadiaria/communication-bridge
Description: Test communication bridge in ios and android
Author: giovani
Latest version: 1.0.8

# communication-bridge

Test communication bridge in ios and android

## Installation

```sh
npm install communication-bridge
```

## Usage

```js
import CommunicationBridge from "communication-bridge";

// ...

const result = await CommunicationBridge.multiply(3, 7);
```

## Contributing

See the [contributing guide](CONTRIBUTING.md) to learn how to contribute to the repository and the development workflow.

## License

MIT
npm package: @giovanibrioni/serverless-plugin-kong
Description: Serverless framework plugin to configure Kong.
Author: Alois
Latest version: 0.0.8

# serverless-plugin-kong

[Serverless framework](https://www.serverless.com) plugin to configure a Kong API Gateway cluster.

## Installation

```bash
$ npm install @giovanibrioni/serverless-plugin-kong
```

## Usage

Add the plugin to `serverless.yml`

```yaml
# serverless.yml

plugins:
  - serverless-plugin-kong
```

Add an event of type `kong` to your functions in `serverless.yml`. Configure the route with the `route` property. The `aws-lambda` plugin will be automatically configured.

```yaml
# serverless.yml

service: example

functions:
  hello:
    handler: handler.hello
    events:
      - kong:
          route:
            methods:
              - GET
            paths:
              - /
            protocols:
              - http
```

Add configuration options to custom section of `serverless.yml`.

```yaml
# serverless.yml
custom:
  kong:
    admin_api_url: http://localhost:8001
    lambda:
      config:
        aws_key: ${env:AWS_ACCESS_KEY_ID, 'asdf'}
        aws_secret: ${env:AWS_SECRET_ACCESS_KEY, 'asdf'}
```

You can add additional plugins to a route by setting the `plugins` property on the event.
```yaml
functions:
  hello:
    handler: handler.hello
    events:
      - kong:
          route:
            methods:
              - GET
            paths:
              - /
            protocols:
              - http

          plugins:
            - name: basic-auth
              enabled: true
              config:
                hide_credentials: true
            - name: correlation-id
              enabled: true
```

## Contributing

Pull requests welcome! Please fork the repo and submit your PR.
npm package: @giovannapilon/mylib
Description: A small SVG generator lib (example module) - @giovannapilon/mylib
Author: giovannapilon
Latest version: 1.0.1

# @giovannapilon/mylib

A small example Node.js module that creates simple SVGs using a key string. It is intended as an illustrative example for learning how to create an NPM module with ESM imports and export a default object.

## Usage

Install (when published):
```
npm install @giovannapilon/mylib
```

Use:
```js
import lib from '@giovannapilon/mylib';

console.log(lib.getSVG('giovanna'));
```

Local test:
```
cd mylib
node ./teste.js ana123
```

Local development (link the module so it can be used in another local project):
```
# inside mylib
npm link

# inside consumer project folder
npm link @giovannapilon/mylib
```

You can also create a tarball and try to install it in a local test project:
```
# inside mylib
npm pack
# then in consumer project
npm install ../path/to/@giovannapilon-mylib-1.0.0.tgz
```

## Publish
1. Log in to NPM: `npm login`
2. Check if the package name is available: `npm view @giovannapilon/mylib`
3. Publish: `npm publish --access public`
4. If publishing a new version, update `version` in `package.json`.

## Notes & Good Practices
- The package is scoped under `@giovannapilon`.
- `type: "module"` enables ESM imports/exports.
- Ensure your git repo is initialized and in sync with GitHub before publishing.
- Add `repository` and `bugs` fields to `package.json` so users can see where to file issues.
- Consider a `prepublishOnly` script to run tests/builds automatically before publishing.
npm package: @giovannicapizzi/gitview
Description: Open useful web pages of a git repository.
Author: Giovanni Capizzi
Latest version: 1.0.4

# GitView

A simple binary to open useful web pages of a git repository. 
Currently tested with: `Gitea`, `Github`, `Gitlab` and `BitBucket` (partially).

## Usage:

```bash
gitview [options]            
```

### Options

``` bash
-c, --commit    Show the latest commit page of the project. 
-h, --home      Show the homepage of the git endpoint.      
-i, --issues    Show the issues page of the project.        
-p, --page      Show the git page of the project.           
-u, --url       Display the url of the project.             
--help          Display this help message.      
```

### Install

```bash
npm i -g @giovannicapizzi/gitview
```
npm package: @giovannicardamone/eslint-config
Description: My Eslint Configuration for node
Author: Giovanni Cardamone
Latest version: 0.6.0

# eslintc

[![CI](https://github.com/GiovanniCardamone/eslint-config/actions/workflows/npm-ci.yml/badge.svg)](https://github.com/GiovanniCardamone/eslint-config/actions/workflows/npm-ci.yml)
[![NPM version](https://img.shields.io/npm/v/@giovannicardamone/eslint-config.svg?style=plastic)](https://www.npmjs.com/package/@giovannicardamone/eslint-config)
[![NPM downloads](https://img.shields.io/npm/dm/@giovannicardamone/eslint-config.svg?style=plastic)](https://www.npmjs.com/package/@giovannicardamone/eslint-config)

My Eslint Configuration

## :information_source: Features

- es2021
- typescript
- prettier
- node
- browser
- mocha

## :package: Installation

Install package

```bash
  npm i -D @giovannicardamone/eslint-config
```

Install required dev dependencies

```bash
  npm i -D eslint @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint-config-prettier
```

Add eslintrc configuration in your `package.json`

```json
{
  "name": "your-beautiful-package",
  "eslintConfig": {
    "extends": "@giovannicardamone/eslint-config"
  }
}
```
npm package: @giovannicardamone/prettier-config
Description: My Prettier configuration
Author: Giovanni Cardamone
Latest version: 0.1.3

# prettierrc

My Prettier configuration

## :package: Installation

[![CI](https://github.com/GiovanniCardamone/prettier-config/actions/workflows/npm-ci.yml/badge.svg)](https://github.com/GiovanniCardamone/prettier-config/actions/workflows/npm-ci.yml)
[![NPM version](https://img.shields.io/npm/v/@giovannicardamone/prettier-config.svg?style=plastic)](https://www.npmjs.com/package/@giovannicardamone/prettier-config)
[![NPM downloads](https://img.shields.io/npm/dm/@giovannicardamone/prettier-config.svg?style=plastic)](https://www.npmjs.com/package/@giovannicardamone/prettier-config)

Install package

```bash
npm i -D @giovannicardamone/prettier-config
```

Install required dev dependencies

```bash
  npm i -D prettier
```

Add prettier configuration in your `package.json`

```json
{
  "name": "your-beautiful-package",
  "prettier": "@giovannicardamone/prettier-config"
}
```