Package Manager & Publishing Guide

How to bundle, validate, and publish packages to the official NextViper Package Registry.

NextViper Package Manager & Publishing

Complete guide to creating, distributing, and consuming packages via the official NextViper Package Registry (https://nextviper.nuratix.com).

1. Manifest: `nextviper.toml`

Every package contains a manifest in the project root:

toml

[project]
name = "matrix_tools"
version = "1.0.0"
description = "Fast sparse matrix factorizations and solvers"
license = "MIT"
authors = ["Jane Developer <jane@example.com>"]
repository = "https://github.com/janedev/matrix_tools"
homepage = "https://nextviper.nuratix.com/packages/matrix_tools"

[dependencies]
tensor = "^1.0.0"
data = "^1.0.0"

[dev-dependencies]
test_runner = "^0.2.0"

2. Publishing Workflow

Step 1: Obtain API Token

Step 2: Authenticate CLI

bash

nextviper login --token nv_8f3d1b2c4e5a6f...

Step 3: Publish Package

bash

nextviper publish

The CLI will:

Validate nextviper.toml and SemVer string.

Ensure no malicious path traversals (../) exist.

Bundle source files into a .nvpkg gzip tarball.

Calculate cryptographic SHA-256 tree checksum.

Upload archive and register the immutable version.