# What Is the Package Version of i-have-adhd? A Guide to Version 0.3.0

> Discover the current package version of i-have-adhd, which is 0.3.0. Learn where to find this information in the package.json file.

- Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd)
- Tags: api-reference
- Published: 2026-09-12

---

**The current package version of i-have-adhd is 0.3.0, defined on line 3 of the [`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json) manifest file in the repository root.**

The i-have-adhd repository by ayghri uses standard Node.js versioning conventions to track releases and synchronize internal tooling. Understanding the package version is essential for managing dependencies across TypeScript extensions and runtime adapters. This guide explains where to find the current version, how to interpret the semantic versioning scheme, and how to access version data programmatically.

## Locating the Package Version in package.json

The canonical source of truth for the package version resides in the repository's **[`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json)** file. According to the ayghri/i-have-adhd source code, line 3 of this manifest declares the version as `0.3.0`.

This repository follows the **MAJOR.MINOR.PATCH** semantic versioning scheme:

- **MAJOR (0)** – Indicates initial development where breaking changes may occur.
- **MINOR (3)** – Represents new functionality added in a backward-compatible manner.
- **PATCH (0)** – Reserved for backward-compatible bug fixes.

Because the package is marked as `"private": true` in the manifest, the version number primarily serves internal tooling workflows—including OMP and Pi extensions—rather than public npm distribution.

## Accessing the Version Programmatically

Developers can retrieve the package version of i-have-adhd at runtime using several approaches, depending on the environment.

### Node.js Require Statement

Use the standard CommonJS require pattern to load the manifest from any JavaScript file:

```javascript
// Load the package manifest
const pkg = require('../package.json');

// Output the current version
console.log(`i-have-adhd version: ${pkg.version}`);
// → i-have-adhd version: 0.3.0

```

### TypeScript Extension Integration

For TypeScript extensions like those implemented in [`extensions/i-have-adhd.ts`](https://github.com/ayghri/i-have-adhd/blob/main/extensions/i-have-adhd.ts), import the JSON module directly to expose the version via runtime hooks:

```typescript
import pkg from '../package.json';

export const ADHD_VERSION = pkg.version as const;

// Example: expose version via a runtime hook
export function getVersion() {
  return ADHD_VERSION;
}

```

### Command Line Interface

Retrieve the version without modifying source files using Node's evaluation flag:

```bash
node -e "console.log(require('../package.json').version)"

# prints: 0.3.0

```

## Version Implications for Extensions and Runtime

The version declared in [`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json) synchronizes behavior across the project's runtime environments. When the version bumps, dependent runtime adapters must be re-validated to ensure compatibility with the skill definition files located in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md).

Since the repository maintains a private status, version increments track internal milestones for the OMP and Pi extension ecosystems rather than public API changes. Always verify that [`extensions/i-have-adhd.ts`](https://github.com/ayghri/i-have-adhd/blob/main/extensions/i-have-adhd.ts) aligns with the current manifest version before deploying updates.

## Summary

- The **i-have-adhd** package version is **0.3.0**, located on line 3 of [`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json).
- The project uses **semantic versioning** (MAJOR.MINOR.PATCH) with MAJOR at 0 indicating initial development.
- Access the version programmatically via `require('../package.json').version` in Node.js or ES6 imports in TypeScript.
- Version bumps require validation of runtime adapters in [`extensions/i-have-adhd.ts`](https://github.com/ayghri/i-have-adhd/blob/main/extensions/i-have-adhd.ts) to maintain compatibility with skill definitions.
- The `"private": true` flag means this version is for internal tooling only, not npm publication.

## Frequently Asked Questions

### What is the current package version of i-have-adhd?

The current package version is **0.3.0**, as specified in line 3 of the [`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json) file in the repository root.

### Where is the i-have-adhd version number defined?

The version number is defined in the repository's **[`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json)** manifest file. This serves as the single source of truth for all tooling, extensions, and runtime adapters consuming the package.

### How can I check the i-have-adhd version from code?

You can access the version programmatically by importing or requiring the [`package.json`](https://github.com/ayghri/i-have-adhd/blob/main/package.json) file and reading the `.version` property. This works in both Node.js CommonJS (`require`) and TypeScript ES6 (`import`) environments, as well as via one-line CLI commands.

### Does i-have-adhd follow semantic versioning?

Yes, the repository follows the **MAJOR.MINOR.PATCH** convention. Version 0.3.0 indicates initial development (MAJOR 0), three minor feature releases (MINOR 3), and no patch-level bug fixes (PATCH 0) in the current release cycle.