Inkforge v0.1.5

What is new in v0.1.5

A fix and security release.

Fixed

• emit no longer overwrites the generated article with the raw input when INKFORGE_CONTENT_DIR does not end in articles. The inputs directory is derived from the last path segment (sibling inputs/ for a directory named articles, <dir>/inputs/ otherwise) and a guard refuses to ever write the raw input to the article's own path. Five regression tests cover both layouts, a name that merely ends in articles, and the guard (#63, #68)
• inkforge generate exits after a successful run in interactive terminals. The stage spinner is recoloured at the emit stage instead of being replaced by a second spinner whose timer kept the process alive (#68)

Security

• Dependency advisories patched so pnpm audit is clean at every severity and the CI Security Audit job is green again (#67): next 16.3.3 → 16.3.8 (critical RCE in next/og, high SSRF in Image Optimization, four moderate cache and leak advisories, one low), sharp 0.35.4 → 0.35.5 (librsvg CVE-2026-96889), source-map-js 1.2.1 → 1.2.2 (event-loop DoS), vitest / @vitest/mocker 4.1.9 → 4.1.11 (path traversal). Supersedes Dependabot #59 and #60.

Full changelog: https://github.com/sairam0424/Inkforge/blob/main/CHANGELOG.md
Compare: v0.1.4...v0.1.5

Inkforge v0.1.4

What is new in v0.1.4

A documentation release: the repository now describes what the code actually does.

README and repository presentation

• Root README.md rewritten to the Standard Readme order: dynamic badges only (CI, CodeQL, OpenSSF Scorecard, release, license), table of contents, Quick Start, Install and Run Options, full generate/publish/list flag tables, every environment variable the code reads, Mermaid pipeline diagram, LLM fallback chains as implemented, Supported Platforms table and an honest Status and Roadmap section (#62)
• packages/cli/README.md and packages/core/README.md rewritten against the source; new apps/web/README.md and docs/README.md index (#62)
• docs/assets/demo.svg: a real inkforge generate run recorded with asciinema and rendered with svg-term; docs/assets/social-preview.{html,png} for the repository social preview (#62)
• One short description everywhere (README, package.json, apps/web/package.json, GitHub About), 20 descriptive GitHub topics, and inkforge --help now prints the CLI package description instead of the old "human-readable MDX" tagline (#62)

Documentation corrections from review

• --title semantics, pnpm lint (no linter wired up), make ci local audit is advisory, the web app writes relative to apps/web, Dev.to tag drop rule, --platform substack rejection, Node 20.9 floor from Next.js 16, Commander exit codes, Makefile .env parsing, make publish-status scope
• SECURITY.md, CONTRIBUTING.md, docs/architecture.md and docs/publishing.md aligned with the code

Known issues

• emit overwrites the generated article with the raw input when INKFORGE_CONTENT_DIR does not end in articles (#63)
• inkforge generate does not exit in an interactive terminal because the stage spinner is never stopped
• The CI dependency audit is still red on the apps/web advisories listed under v0.1.3; Dependabot #59/#60 (next 16.3.8) are pending

Full changelog: https://github.com/sairam0424/Inkforge/blob/main/CHANGELOG.md
Compare: v0.1.3...v0.1.4

Inkforge v0.1.3

What is new in v0.1.3

Content pipeline

• Combined release article for tracehub-mcp v0.12.3 + cost-guard-mcp v0.3.3 (#56) — Dev.to and Substack live; single LinkedIn post listing every surface each server is live on (18 verified links); 5-GIF plan embedded in the body in the single-line ![description](direct-url) format
• trelix v3.2.2 → v3.3.8 release article (#53) — Dev.to and Substack live
• MindForge v12.0.0 first-user-release launch article (#52) — Dev.to and Substack live
• trelix v3.1.1 and v3.2.1 release articles — Dev.to, Substack and LinkedIn
• Backlog publish: "How I Built Inkforge" (Dev.to draft) plus DNS and Inkforge platform tracking files

Publishers

• Medium and Hashnode browser-harness publishers in @inkforge/core (#46)

CI and tooling

• CodeQL, OSSF Scorecard and gitleaks workflows; dependency audit gate (pnpm audit --audit-level high) enforced in CI (#49)
• Dependabot configuration for npm and GitHub Actions
• GitHub Actions SHA-pinned with explicit least-privilege permissions
• Tailored CodeRabbit review configuration (#47)

Dependency updates

• next 16.2.9 → 16.2.11 → 16.3.3 to patch transitive postcss and sharp CVEs (#30, #40)
• @tailwindcss/postcss 4.3.1 → 4.3.3 (#39)

Known issue (security)

• The CI dependency audit currently fails on advisories published after 2026-09-26 in apps/web's tree: next@16.3.3 (SSRF in Image Optimization, RCE in next/og; fixed in ≥16.3.8), sharp@0.35.4 (librsvg, fixed in ≥0.35.5), source-map-js, vitest. Dependency bumps are tracked for the next release and are unrelated to the content in this one.

Published articles

• tracehub-mcp v0.12.3 + cost-guard-mcp v0.3.3 combined release — Dev.to, Substack, LinkedIn
• trelix v3.2.2 → v3.3.8 release — Dev.to, Substack
• MindForge v12.0.0 launch — Dev.to, Substack
• trelix v3.1.1 and v3.2.1 releases — Dev.to, Substack, LinkedIn
• How I Built Inkforge — Dev.to (draft)

Full changelog: https://github.com/sairam0424/Inkforge/blob/main/CHANGELOG.md
Compare: v0.1.2...v0.1.3

Inkforge v0.1.2

What is new in v0.1.2

Tombstone v1.0 launch pipeline

• Generated 3,531-word narrative article via STORM pipeline from personal on-call incident notes
• Dev.to live, Substack live, LinkedIn live (15-slide HQ carousel at 2x pixel density)
• Medium + Hashnode in backlog
• Cover image 1400x787px, GIF plan with Giphy keywords
• LinkedIn single combined post based on 104-agent deep research (carousel = 7.00% engagement)

CLI fix

• inkforge generate --code <dir> now walks directory trees (max 10 files), skipping node_modules/dist/.next, collecting .ts/.tsx/.js/.jsx/.py/.go/.rs with file-path headers

DX — Makefile

• 27 targets across 9 groups: Setup, Build, Quality, Generate, Publish, Content, Cleanup, Extras
• make generate TOPIC="..." TONE=senior wraps full STORM pipeline
• make ci mirrors GitHub Actions locally
• make env-check prints green/red status for all required env vars

Bug fixes

• Correct GitHub URL sairam0424/Tombstone across all content
• Correct npm package name @tombstone/core
• Version references updated to v2.2.0 (Dashboard v1.0.0)
• Removed broken GIF placeholder images from Dev.to article

Published articles

• Feature Flags at Scale — Dev.to, Substack, LinkedIn (carousel)
• How I Built Tombstone — Dev.to, Substack, LinkedIn
• How I Traced One Browser Request — Dev.to, Medium, Hashnode, Substack
• How DNS Works — Dev.to, Hashnode

Full changelog: https://github.com/sairam0424/Inkforge/blob/main/CHANGELOG.md

⚒ Inkforge v0.1.0 — Initial Release

⚒ Inkforge v0.1.0

AI-powered article generation system. Takes notes, topics, or code → produces structured, human-readable Markdown articles ready to publish.

What's included

@inkforge/core — STORM two-stage generation pipeline

• Ingest (notes/topic/code) → Outline → Draft → Polish → Emit
• BM25 in-memory RAG over personal knowledge base
• LLM: AWS Bedrock Sonnet 4.6 → Haiku 4.5 fallback chain
• Publishers: Dev.to (REST) + Hashnode (GraphQL v2) with canonical URL
• 11/11 tests passing ✅

@inkforge/cli — Terminal interface

• inkforge generate — 3 input modes, tone × format × length × category
• inkforge publish — one command to Dev.to or Hashnode
• inkforge list — article library overview

@inkforge/web — Next.js 16 + Tailwind v4 web UI

• Live streaming article preview via SSE
• Animated dial selectors with Motion spring physics
• Article library with format filters and publish buttons
• 10 routes, 0 TypeScript errors

Quick Start

git clone https://github.com/sairam0424/Inkforge.git
cd Inkforge
pnpm install
cp .env.example .env  # fill in your LLM credentials
node packages/cli/dist/index.js generate --topic "Your topic here" --tone senior --format explainer

Links

• 📖 Article: How I Traced One Browser Request — first article generated with Inkforge
• 🌐 Portfolio: anvilry.vercel.app