open-index/open-npm huggingface dataset:
npm package: @francocanzani/ai-commit
Description: A package that generates commit messages with AI
Author: Franco Canzani
Latest version: 1.1.3

# ai-commit

## Overview

`ai-commit` is an AI-powered Git commit message generator that assists developers in creating meaningful and structured commit messages using OpenAI or Anthropic's AI models. The tool analyzes the differences in staged changes and generates a proposed commit message based on configurable parameters.

## Features

- Generates commit messages based on staged changes.
- Supports multiple AI providers (OpenAI and Anthropic).
- Configurable commit message formats and languages.
- Allows auto-commit and preview options.

## Installation

To install `ai-commit`, run:

```bash
npm install ai-commit
```

## Usage

To use the tool, you can run it directly from the command line:

```bash
npx ai-commit
```

### Commands

- **Generate commit message for staged changes:**

  ```bash
  npx ai-commit
  ```

- **Configure ai-commit settings:**
  ```bash
  npx ai-commit --config
  ```

## Configuration

The configuration settings can be defined in the `ai-commit-rc.json` file. The tool will attempt to read this file when executed. Here’s an example of the default configuration:

```json
{
  "provider": "openai",
  "envVariable": "OPENAI_API_KEY",
  "format": "Conventional (type(scope): description)",
  "language": "english",
  "maxLength": 50,
  "options": {
    "showDiff": false,
    "autoCommit": false
  }
}
```

### Default Configuration

If you choose not to set up a configuration, the default settings are as follows:

- **AI Provider:** OpenAI (API key will be extracted from the environment variable `OPENAI_API_KEY`)
- **Format:** Simple descriptions
- **Length:** 50 characters maximum
- **Language:** English
- **Auto commit:** disabled

### API Key Management

- Never store API keys directly in your code or config files.
- Use environment variables to manage your API keys securely.
- Add `.env` to your `.gitignore` to avoid accidental exposure of your API keys.

## Example Usage

1. Run `ai-commit-config` to set up your preferences or let the tool use the default configuration.
2. Stage your changes using `git add`.
3. Execute `ai-commit` to generate a commit message based on the staged changes.
4. Confirm the proposed commit message or auto-commit based on your settings.

## Contributing

Contributions are welcome! Please feel free to open issues or submit pull requests.

## License

This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.
npm package: @francocorrea/cov-vaccine-uy-validate
Description: A library to validate the COVID-19 vaccine certificate issued by the Uruguayan government.
Author: Franco Correa
Latest version: 1.0.0

# @francocorrea/cov-vaccine-uy-validate

A library to validate the COVID-19 vaccine certificate issued by the Uruguayan government.

## Compatibility

Should work in Node, React Native and Web (through WebCrypto). Only React Native has been tested.

## Usage

```ts
import { verify } from '@francocorrea/cov-vaccine-uy-validate';

const data = 'HC1:(...)' // Data obtained from scanning the QR code

const results = await verify(data);
/*
    {
      "valid": true, // if false, the digital signature verification has failed
      "data": {
        "Date": "2021-08-01",
        "Name": "Nombres Apellidos",
        "CountryCode": "858",
        "DocumentType": "CI",
        "DocumentNumber": "11111111",
        "VaccinationInfo": {
            "Doses": [
                {
                    "Number": 2,
                    "Date": "2021-07-01",
                    "Vaccine": "PFIZER"
                },
                {
                    "Number": 2,
                    "Date": "2021-06-01",
                    "Vaccine": "PFIZER"
                },
            ] 
        }
    }
 */
```
npm package: @francoecp/test-mcp-server
Description: Sample MCP Server
Author: Esteban Córdoba
Latest version: 0.0.3

# @francoecp/test-mcp-server

A sample Model Context Protocol (MCP) server implementation that provides a simple weather service.

## Description

This is a test package that demonstrates how to create a basic MCP server using the `@modelcontextprotocol/sdk`. The server implements a simple weather service that returns mock weather data for any given city.

## Installation

You can run this package directly using npx:

```bash
npx -y @francoecp/test-mcp-server@latest
```

## Features

- Simple MCP server implementation
- Mock weather service endpoint
- Built with TypeScript
- Uses Express.js and Zod for type validation

## Available Tools

### getWeather

Returns mock weather information for a specified city.

Parameters:
- `city` (string): The name of the city to get weather information for

Response:
- Returns a message indicating sunny weather for the specified city

## Development

To set up the development environment:

1. Clone the repository
2. Install dependencies:
```bash
npm install
```
3. Build the project:
```bash
npm run build
```

## License

MIT

## Author

Esteban Córdoba
npm package: @francoisdebellescize/homebridge-sure-petcare-platform
Description: Enables Sure Petcare products (currently only doors) to work with Homekit. If you would like to see their other accessories supported feel free to reach out through this repo or to submit a pull request.
Author: Wylan Swets
Latest version: 0.1.10

# homebridge-sure-petcare-platform

Enables Sure Petcare products (currently only doors) to work with Homekit. If you would like to see their other accessories supported feel free to reach out through this repo or to submit a pull request.

To install:

    npm install -g homebridge-sure-petcare-platform

To configure, add this to your homebridge config.json file:
    
    
    "platforms": [
        {
            "platform": "SurePetcare",
            "email": "your_email@email.com",
            "password": "your_password",
            "poll_interval": 30,
            "pet_occupancy": true,
            "occupancy_flipped": true,
            "lock_mode": 1
        }
    ]

### Note:
#### poll_interval (optional) 
If poll_interval it is not defined in the config it will default to 30. Adjusting this number will lengthen or shorten the amount of time between status checks for each accessory. I would recommend keeping this to above 5 seconds, but feel free to adjust this to your liking.

#### pet_occupancy (optional)
pet_occupancy will default to false. If this is true it will enable an occupancy sensor for each of your pets. During each "poll interval" the occupancy sensor will be updated to reflect if the app says the pet is inside or outside the house. "Occupancy Detected" means they are inside the house, "No Occupancy" means they are outside the house.

#### occupancy_flipped (optional)
occupancy_flipped will default to false. If you set this to true, the occupancy sensors state will be flipped. This means if your pet is outside, the sensor will read "occupancy detected". If a pet is inside the house occupancy will not be detected.

#### lock_mode (optional)
lock_mode will default to 1 if not defined. You can change this value based on the locking mode you want. The different modes are:
* 1 (default) - Keeps your pets inside the house, but will let them enter from outside.
* 2 - Keeps your pets outside the house, but will let them go outside. (keeps dead lizards and mice out)
* 3 - Locks the door in both directions. No one in, no one out. (keeps lizards and mice alive and from dying and being brought in)

## Supports:
* Cat Door Connect
* Pet Door Connect

## Change Log:
### 0.1.4 - Oct. 6, 2020
* Wired in lock_mode to actually work becuase who needs to test code you write?

### 0.1.3 - Oct. 6, 2020
* Added lock_mode support to specify how the pet doors would lock from homekit.
npm package: @francoisdebellescize/sure_petcare
Description: NodeJS API library for Sure Petcare pet door
Author: Wylan Swets & Jostein Kjønigsen
Latest version: 0.0.7

# sure_petcare
NodeJS API library for Sure Petcare pet door


### Note on battery info:

Sure Petcare products use 4x AA or 4x C batteries. This is important when reading their battery info and interpreting what it means.

Both AA and C batteries that are non-rechargable have a standard nominal voltage of 1.5v when fully charged. Most embedded computers / electronics run on 5V. When you put 4x 1.5v batteries together you get 6v in total.

As a battery is consumed the voltage will drop lower and lower, which is also a fairly decent way to determine the charge level. Taking in to account that the product most likely runs at 5v and cuts out / doesn't run below 5v, we need to consider the batteries depleted at 5v.

The Sure Petcare api returns a number that seems to indicate the overal voltage being read from the batteries, which is why 6 and higher always shows 100% charge in the app, and closer and closer to 5 shows progressively less charge percentage.

That said, this plugin has a helper function (translateBatteryToPercent) that will convert this number to a percentage based on these findings, and will convert it in to a rounded integer value representing the percentage from 0 to 100% (0% being 5v).

Some sample data from when I was observing the data from the API and what was happening in the app:

Shows 100%:
6.121
6.108
6.044
5.956

Shows 50%:
5.334
5.182
5.134

Shows 25% (and recommends changing the battery soon in the app):
5.01