open-index/open-npm huggingface dataset:
npm package: @sailboat-computer/common-types
Description: Common types for Sailboat Computer v3
Author: Sailboat Computer Team
Latest version: 1.1.21
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @sailboat-computer/common-types

This package provides centralized type definitions for the Sailboat Computer v3 project. It serves as the single source of truth for common types used across all packages.

## Installation

```bash
npm install @sailboat-computer/common-types
```

## Usage

```typescript
import { 
  AlertSeverity, 
  EventPriority, 
  CircuitBreakerState,
  OperationalContext,
  MarineFailureType,
  MarineSystemType,
  TimeRange,
  MarineEnvironmentStatus
} from '@sailboat-computer/common-types';

// Use the types in your code
const severity: AlertSeverity = AlertSeverity.WARNING;
const context: OperationalContext = OperationalContext.SAILING;
```

## Available Types

### Enums

- `AlertSeverity` - Severity levels for alerts
- `EventPriority` - Priority levels for events
- `EventCategory` - Categories for events
- `APIErrorCode` - Standard error codes for API responses
- `HealthStatus` - Health status indicators for services and components
- `CircuitBreakerState` - States for circuit breaker pattern implementation
- `OperationalContext` - Operational contexts for marine environment
- `MarineFailureType` - Types of failures common in marine environment
- `MarineSystemType` - Types of marine systems for categorization

### Interfaces

- `TimeRange` - Represents a time range with start and end times
- `MarineEnvironmentStatus` - Current marine environment conditions

## Development

This package is automatically generated from contract definitions. Do not edit the type files directly.

To update the types:

1. Edit the contract definitions in `contracts/common/common-enums.md`
2. Run the type generator:

```bash
./build-types-v2.sh --single common/common-enums.md
```

3. Build the package:

```bash
cd packages/common-types
npm run build
```

## License

MIT
npm package: @sailboat-computer/types-service-based
Description: Generated TypeScript types for sailboat computer v3 services.
Author: Sailboat Computer Team
Latest version: 1.1.21
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @sailboat-computer/types-service-based

Generated TypeScript types for sailboat computer v3 services.

## Overview

This package contains TypeScript type definitions generated from the contract files in the sailboat computer v3 project. It provides strongly-typed interfaces, enums, and types for all services in the system.

## Installation

```bash
npm install @sailboat-computer/types-service-based
```

## Usage

Import types from specific services:

```typescript
// Import common types
import { AlertSeverity, EventPriority } from '@sailboat-computer/types-service-based/common';

// Import service-specific types
import { SensorData } from '@sailboat-computer/types-service-based/hardware-interface';
import { VesselState } from '@sailboat-computer/types-service-based/state-manager';
```

## Directory Structure

The package is organized by service:

- `common/` - Common types used across all services
- `hardware-interface/` - Hardware interface service types
- `state-manager/` - State manager service types
- `data-manager/` - Data manager service types
- `safety/` - Safety service types
- etc.

## Development

This package is automatically generated from the contract files in the sailboat computer v3 project. Do not edit the files in this package directly.

To regenerate the types:

```bash
npm run build:types
```

## License

MIT
npm package: @sailboat-computer/validation
Description: Validation framework for sailboat computer v3
Author: Sailboat Computer Team
Latest version: 1.1.56

# @sailboat-computer/validation

Validation framework for sailboat computer v3 with marine-specific rules and data quality assessment.

## Overview

This package provides a comprehensive validation framework designed specifically for marine environments. It includes:

- **Multi-layer validation strategy** (Physical → Operational → Quality)
- **Marine-specific validation rules** for all sensor types
- **Cross-sensor validation** and consistency checks
- **Data source prioritization** and confidence scoring
- **Performance optimization** with batch processing and caching

## Current Status

✅ **Phase 1 Complete**: Core types and interfaces defined
🔄 **Phase 2 In Progress**: Implementation of validation engine and rules

### Completed Features

- Comprehensive TypeScript type definitions
- Marine-specific validation ranges for:
  - Navigation sensors (GPS, compass, wind, depth)
  - Environmental sensors (temperature, pressure, humidity)
  - Electrical systems (48V/12V batteries, solar)
  - Engine and mechanical systems
  - Fluid systems (watermaker, tanks, anchor)
- Validation result structures
- Confidence calculation framework
- Sensor health assessment interfaces
- Data source prioritization configuration

### Planned Features

- [ ] Physical validation layer implementation
- [ ] Operational validation layer implementation
- [ ] Quality assessment layer implementation
- [ ] Marine-specific validation rules
- [ ] Cross-sensor validation engine
- [ ] Data source prioritization engine
- [ ] Performance optimization features
- [ ] Health monitoring integration

## Installation

```bash
npm install @sailboat-computer/validation
```

## Usage

```typescript
import { 
  ValidationResult, 
  RawSensorData, 
  ValidatedSensorData,
  MarineValidationRanges 
} from '@sailboat-computer/validation';

// Example usage will be added when implementation is complete
```

## Marine-Specific Features

### Physical Validation
- Range validation based on marine equipment specifications
- Rate of change validation for sensor readings
- Sensor specification compliance checking

### Operational Validation
- Context-dependent validation (sailing vs anchored vs maintenance)
- Cross-sensor consistency checks
- Temporal consistency validation

### Quality Assessment
- Confidence scoring based on multiple factors
- Sensor health assessment
- Data source prioritization

## Architecture

The validation framework follows a three-layer architecture:

1. **Physical Layer**: Basic range and specification validation
2. **Operational Layer**: Context-aware and cross-sensor validation
3. **Quality Layer**: Confidence scoring and source prioritization

## Development

```bash
# Build the package
npm run build

# Run tests
npm test

# Watch mode for development
npm run build:watch
```

## Contributing

This package is part of the sailboat computer v3 project. Please follow the contract-first development approach and ensure all changes are properly tested.

## License

MIT
npm package: @sailci/psx-components-branch
Description: ### Overview
Latest version: 0.2.0

# Branch

### Overview

The Branch component is useful for running any of its child components on specified Git branches.

### Valid Props

| Name | Type   | Example  | Notes                               |
| :--- | :----- | :------- | :---------------------------------- |
| when | string | ^master$ | Should be a valid RegExp expression |

### Example Usage

```js
<Branch when="^master$">
  <Run command="echo on master branch!" />
</Branch>
```
npm package: @sailci/psx-components-run
Description: ### Overview
Latest version: 0.1.1

# Run

### Overview

The Run component is a general purpose command that executes relevant shell / terminal commands using spawn.

### Valid Props

| Name    | Type   | Example            |
| :------ | :----- | :----------------- |
| command | string | echo Hello World   |

### Example Usage

```js
<Run command="echo Hello World" />
```
npm package: @sailci/psx-components-slack
Description: ### Overview
Latest version: 0.2.0

# Slack

### Overview

The Slack component will report success or failure for any of the components it wraps.

### Valid Props

| Name    | Type   | Example                                                  |
| :------ | :----- | :------------------------------------------------------- |
| webhook | string | '$SLACK_WEBHOOK' or 'https://hooks.slack.com/services/…' |

If you have set your Slack webhook as an environment variable then supplying the `webhook` prop with the name of the environment variable prefixed with `$` will cause the Slack component to use that instead.

### Example Usage

```js
<job>
  <Slack webhook="https://hooks.slack.com/services/…">
    <Run command="yarn" />
    <Run command="yarn lint" />
    <Run command="yarn test" />
  </Slack>
</job>
```
npm package: @sailci/psx-components-zeit-now
Description: ### Overview
Latest version: 0.5.0

# ZeitNow

### Overview

The ZeitNow component is a simple wrapper around the Zeit now CLI.

### Valid Props

| Name  | Type                        | Example     | Notes                                |
| :---- | :-------------------------- | :---------- | :----------------------------------- |
| token | string                      | $ZEIT_TOKEN | Should be a valid Zeit token         |
| alias | ?string                     | domain      | Your domain name to alias deployment |
| paths | ?string \| ?Array\<string\> | public      | Path to folder for deployment        |

You can also pass any of the many options that you normally would to the
[Now CLI](https://zeit.co/docs/features/now-cli) for deploying and aliasing. For the `env`
option, just like `token`, any value beginning with `$` will be substituted for its value
from the current environment variables so you can keep them secret.

### Example Usage

Generate a secret using [`sail secret`](http://docs.sail.sh/guides/cli-commands/sail-secret-file).

```js
<pipeline>
  <environment>
    <variable secret name="MONGO_URL" value="generated-secret-value" />
    <variable secret name="MY_API_TOKEN" value="generated-secret-value" />
    <variable secret name="ZEIT_TOKEN" value="generated-secret-value" />
  </environment>
  <job image="node:9.2.1-alpine">
    <ZeitNow
      env={{ MONGO_URL: '$MONGO_URL', MY_API_TOKEN: '$MY_API_TOKEN' }}
      paths="./public"
      public
      regions="bru,sfo"
      token="$ZEIT_TOKEN"
      alias="my-domain.now.sh"
    />
  </job>
</pipeline>
```
npm package: @sailei1996/enumx
Description: `EnumX` 是一个用于 TypeScript 的扩展类，帮助开发者更便捷地管理和操作枚举类型的数据。`EnumX` 提供了一系列访问和操作枚举项的方法，使得代码更具可读性和灵活性，尤其适用于需要字段映射、下拉列表等场景的数据管理。
Latest version: 1.0.8

# EnumX

`EnumX` 是一个用于 TypeScript 的扩展类，帮助开发者更便捷地管理和操作枚举类型的数据。`EnumX` 提供了一系列访问和操作枚举项的方法，使得代码更具可读性和灵活性，尤其适用于需要字段映射、下拉列表等场景的数据管理。

## 特性

- **完善的代码提示**：借助 TypeScript 类型推导，`EnumX` 提供了丰富的代码提示，使得使用更加方便。
- **丰富的枚举项操作方法**：支持通过 `value`、`label`、`alias` 等方式获取对应的枚举项或其属性。
- **简洁的访问**：通过代理机制，可以直接使用枚举的 `alias` 来访问其 `value`。
- **易于集成**：可以直接将 `EnumX` 实例转换为数组，方便用于下拉选择控件等数据源场景。
- **灵活的扩展**：支持自定义枚举项属性，并可以轻松地将其转换为数组。

## 安装

你可以使用 npm 或 yarn 来安装：

```bash
npm install @sailei1996/enumx
# 或者
yarn add @sailei1996/enumx
```

## 使用方法

### 创建 `EnumX` 实例

通过 `EnumX.createEnum` 方法创建 `EnumX` 实例：

```typescript
import EnumX from "@sailei1996/enumx";

const InfoLevelEnum = EnumX.createEnum([
  { label: "通知", alias: "INFO", value: "info", color: "var(--primary-color)" },
  { label: "警告", alias: "WARNING", value: "warning", color: "var(--warning-color)" },
  { label: "错误", alias: "ERROR", value: "error", color: "var(--error-color)" },
] as const);
```

### 常见用法示例

#### 通过 `InfoLevelEnum.alias` 获取对应value，保留enum基本用法：

```typescript
const isInfo = InfoLevelEnum.INFO === "info";
console.log(isInfo); // 输出: true
```

#### 通过 `value` 获取 `label`，适用于字段反显，比如中英文映射：

```typescript
console.log(InfoLevelEnum.getTextFromValue('error')); // 输出: 错误
```

#### 通过 `toArray` 获取数组数据，适用于获取映射数据源，比如下拉选择控件：

```typescript
const InfoLevelList = InfoLevelEnum.toArray();
console.log(InfoLevelList); // 输出原数组

const InfoLevelPartialList = InfoLevelEnum.toArray('INFO', 'ERROR');
console.log(InfoLevelPartialList); // 输出INFO和ERROR组成的数组
```

#### 通过 `fromValue` 获取整条数据：

```typescript
const infoColor = InfoLevelEnum.fromValue("info")?.color;
console.log(infoColor); // 输出: "var(--primary-color)"
```

#### 通过 `GetEnumValueType` 获取枚举类型的value的联合类型：

```typescript
import {GetEnumValueType} from "@sailei1996/enumx";
type InfoLevelValue = GetEnumValueType<typeof InfoLevelEnum>; // 'info' | 'warning' | 'error'
```

### 所有用法示例
```typescript
InfoLevelEnum.INFO // info

InfoLevelEnum.getValueFromAlias('INFO') // info
InfoLevelEnum.getValueFromText('通知') // info

InfoLevelEnum.getAliasFromValue('info') // INFO
InfoLevelEnum.getAliasFromText('通知') // INFO

InfoLevelEnum.getTextFromValue('info') // 通知
InfoLevelEnum.getTextFromAlias('INFO') // 通知

InfoLevelEnum.fromValue('info') // { label: "通知", alias: "INFO", value: "info", color: "var(--primary-color)" }
InfoLevelEnum.fromAlias('INFO') // { label: "通知", alias: "INFO", value: "info", color: "var(--primary-color)" }
InfoLevelEnum.fromText('通知') // { label: "通知", alias: "INFO", value: "info", color: "var(--primary-color)" }

InfoLevelEnum.toArray()

GetEnumValueType<typeof InfoLevelEnum> // 'info' | 'warning' | 'error'
```
npm package: @saileshs/vault-cli
Description: Zero-knowledge password manager CLI - client-side encryption only
Latest version: 1.0.4

# Vault CLI

A secure, zero-knowledge password manager for your terminal.

[![npm version](https://img.shields.io/npm/v/@saileshs/vault-cli.svg)](https://www.npmjs.com/package/@saileshs/vault-cli)

## Installation

```bash
npm install -g @saileshs/vault-cli
```

## Quick Start

```bash
vault signup     # Create account
vault login      # Login
vault add gmail  # Save a password
vault get gmail  # Retrieve it
vault list       # See all entries
```

## Commands

| Command | Description |
|---------|-------------|
| `signup` | Create a new account |
| `login` | Login to your vault |
| `add <label>` | Add a new password |
| `get <label>` | Retrieve a password |
| `list` | List all entries |
| `update <label>` | Update a password |
| `delete <label>` | Delete an entry |
| `logout` | Lock vault |

### Options

```bash
vault get gmail --copy  # Copy to clipboard
vault config --list     # View settings
```

## Security

- **Zero-knowledge architecture**: Your master password is **never sent to the server**
- **Client-side encryption**: All passwords are encrypted locally before upload
- **AES-256-GCM**: Industry-standard encryption
- **Server only stores encrypted data**: Even we can't read your passwords

## License

MIT
npm package: @saileshsahu/create-project
Description: A CLI to bootstrap my new projects
Author: saileshsahu
Latest version: 2.2.1

# zolo-starter-kit

An app to bootstrap Boilerplate projects for Zolo Property Solutions Pvt. Ltd.

## Installation

via NPM:

```sh
npm install -g @saileshsahu/create-project
```

via NPX:

```sh
npx @saileshsahu/create-project
```

## Installation Instructions

> Select template to install when prompted. Installer will automatically install all dependencies for you:
```sh
? Please choose which project template to use (Use arrow keys)
❯ zolo-starter-kit 
```

> Change your directory to /client and run
```sh
> cd client
> npm start
```

Your Boilerplate App should be live on : http://localhost:8080