Version history shows semver compliance

A package stuck at version: 1.0.0 (the npm init default) with no changelog and no git tags has never been intentionally versioned. Consumers cannot tell whether 1.0.0 is stable or a placeholder, and cannot specify version constraints in their package.json with any confidence. Worse, breaking API changes shipped without a major bump silently break consumers on npm update — the canonical semver violation. ISO 25010 modifiability requires that the package's evolution be communicated through its version number.

Set an intentional version and commit to the semver contract.

// Start at 0.1.0 if not yet stable, 1.0.0 when you're ready to commit to backward compat:
{ "version": "0.1.0" }

Semver rules:

• MAJOR (2.0.0): any breaking API change — removed export, changed parameter types, renamed symbol
• MINOR (1.1.0): new exports or features, backward-compatible
• PATCH (1.0.1): bug fixes, no API changes

Use npm version patch|minor|major to bump — it updates package.json and creates a git tag automatically. Version 0.0.0 or a placeholder that was never bumped intentionally fails this check.