open-index/open-npm huggingface dataset:
npm package: @kephrenh/express-request-logger
Description: A customizable Express request logger middleware using Winston and Pino.
Author: Mohamed Amoussa
Latest version: 1.0.3

# Express Request Logger

A customizable Express request logger middleware that combines the power of Winston and Pino for comprehensive request logging.

## Features

- Dual logging with both Winston and Pino
- Automatic request and response logging
- Sensitive data redaction (tokens, passwords, authorization headers)
- Customizable logging format (JSON or pretty-printed)
- Response time tracking
- Status code-based log levels
- TypeScript support

## Installation

```bash
npm install @kephrenh/express-request-logger
```

## Usage

```typescript
import express from "express";
import { createRequestLogger } from "express-request-logger";
import winston from "winston";
import pino from "pino";

const app = express();

// Initialize your loggers
const winstonLogger = winston.createLogger({
  // Your Winston configuration
});

const pinoLogger = pino({
  // Your Pino configuration
});

// Create the request logger middleware
const requestLogger = createRequestLogger({
  tokens: ["accessToken", "refreshToken"], // Optional: tokens to redact
  pinoLogger,
  winstonLogger,
  pretty: true, // Optional: enable pretty printing
  json: false, // Optional: enable JSON format
});

// Use the middleware
app.use(requestLogger);
```

## Configuration Options

| Option        | Type     | Default                         | Description                     |
| ------------- | -------- | ------------------------------- | ------------------------------- |
| tokens        | string[] | ['accessToken', 'refreshToken'] | Array of cookie names to redact |
| pinoLogger    | Pino     | Required                        | Pino logger instance            |
| winstonLogger | Winston  | Required                        | Winston logger instance         |
| pretty        | boolean  | true                            | Enable pretty printing of logs  |
| json          | boolean  | false                           | Enable JSON format for logs     |

## Logged Information

The middleware logs the following information for each request:

- HTTP Method
- Request Path
- Timestamp
- IP Address
- Query Parameters
- Request Body (with sensitive data redaction)
- Cookies (with sensitive tokens redaction)
- Headers (with authorization header redaction)
- Response Status Code
- Response Time

## Security

The middleware automatically redacts sensitive information:

- Passwords in login/register requests
- Authorization headers
- Specified tokens in cookies
- Custom tokens (configurable)

## License

MIT

## Author

Mohamed Amoussa
npm package: @kepi0809/gatsby-source-greenhouse
Description: Gatsby source plugin for loading job posts from greenhouse.io
Author: Diego La Manno
Latest version: 2.0.1

# gatsby-source-greenhouse

> Loads job openings from greenhouse.io into Gatsby.js. Based on [gatsby-source-workable](https://github.com/tumblbug/gatsby-source-workable).

## Status

[![npm version](https://badge.fury.io/js/gatsby-source-greenhouse.svg)](https://badge.fury.io/js/gatsby-source-greenhouse)

## Installation

```bash
npm install gatsby-source-greenhouse
```

or

```bash
yarn add gatsby-source-greenhouse
```

## Usage

To use this source you need to supply a Greenhouse API token. You can create a Greenhouse API token by logging into Greenhouse and going to `Configure > Dev Center > API Credential Management > Create New API Key`. Make sure it is type **Harvest**.

Next, edit `gatsby-config.js` to use the plugin:

```
{
  ...
  plugins: [
    ...
    {
      resolve: `gatsby-source-greenhouse`,
      options: {
        apiToken: `{API_TOKEN}`,
        jobPosts: {
          live: true
        }
      },
    },
  ]
}
```

By default, `gatsby-source-greenhouse` will only retrieve job openings that are marked as _live_. You can change this by passing in `false` in the `jobPosts` plugin option parameter.

## Querying

You can query the all `JobPost` created by the plugin as follows:

```graphql
{
    allGreenhouseJobPost {
        edges {
            node {
                ...
            }
        }
    }
}
```

You can also query all `JobPost` broken out for each department:

```graphql
{
  allGreenhouseDepartment {
    edges {
      node {
        name
        childrenGreenhouseJobPost {
          title
        }
      }
    }
  }
}
```
npm package: @kepi0809/gatsby-source-greenhouse-offices
Description: Gatsby source plugin for loading job posts from greenhouse.io
Author: Diego La Manno
Latest version: 1.0.3

# gatsby-source-greenhouse

> Loads job openings from greenhouse.io into Gatsby.js. Based on [gatsby-source-workable](https://github.com/tumblbug/gatsby-source-workable).

## Status

[![npm version](https://badge.fury.io/js/gatsby-source-greenhouse.svg)](https://badge.fury.io/js/gatsby-source-greenhouse)

## Installation

```bash
npm install gatsby-source-greenhouse
```

or

```bash
yarn add gatsby-source-greenhouse
```

## Usage

To use this source you need to supply a Greenhouse API token. You can create a Greenhouse API token by logging into Greenhouse and going to `Configure > Dev Center > API Credential Management > Create New API Key`. Make sure it is type **Harvest**.

Next, edit `gatsby-config.js` to use the plugin:

```
{
  ...
  plugins: [
    ...
    {
      resolve: `gatsby-source-greenhouse`,
      options: {
        apiToken: `{API_TOKEN}`,
        jobPosts: {
          live: true
        }
      },
    },
  ]
}
```

By default, `gatsby-source-greenhouse` will only retrieve job openings that are marked as _live_. You can change this by passing in `false` in the `jobPosts` plugin option parameter.

## Querying

You can query the all `JobPost` created by the plugin as follows:

```graphql
{
    allGreenhouseJobPost {
        edges {
            node {
                ...
            }
        }
    }
}
```

You can also query all `JobPost` broken out for each department:

```graphql
{
  allGreenhouseDepartment {
    edges {
      node {
        name
        childrenGreenhouseJobPost {
          title
        }
      }
    }
  }
}
```
npm package: @kepi0809/npm-test
Description: A Vue.js component that displays a clock
Author: Anthony Gore
Latest version: 2.0.0

# @kepi0809/npm-test

A Vue component that shows a clock.

This isn't particularly useful, it's used as a demo for how to publish Vue components to NPM!

## Installation

```js
npm i --save-dev @kepi0809/npm-test
```

### Browser

Include the script file, then install the component with `Vue.use(VueClock);` e.g.:

```html
<script type="text/javascript" src="node_modules/vuejs/dist/vue.min.js"></script>
<script type="text/javascript" src="node_modules/@kepi0809/npm-test/dist/vue-clock.min.js"></script>
<script type="text/javascript">
  Vue.use(VueClock);
</script>
```

### Module

```js
import VueClock from '@kepi0809/npm-test';
```

## Usage

Once installed, it can be used in a template as simply as:

```html
<vue-clock></vue-clock>
```