npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

doc-sync-check

v1.3.0

Published

Documentation Drift Detector

Downloads

444

Readme

doc-sync-check

Stop documentation drift in its tracks.

doc-sync-check is a fast, specialized CLI tool that statically analyzes your TypeScript codebase using an Abstract Syntax Tree (AST). It scans your Markdown files for exported symbols and ensures that documented signatures match source code.

If you update a parameter or return type in your code but forget to update the documentation, doc-sync-check will catch it and fail your CI build, reminding your team to keep the docs in sync!

🚀 Installation

You can install doc-sync-check globally, but it is recommended to add it as a devDependency to your project and run it via an npm script or CI pipeline.

npm install -D doc-sync-check

🛠️ Usage

Run doc-sync-check by pointing it to your source code directory and specifying your documentation folder.

npx doc-sync-check <source-dir> --docs <docs-dir>

Options

  • <source-dir>: The root directory containing your TypeScript files.
  • --docs, -d: The path to the folder containing your Markdown documentation files. Defaults to ./docs.
  • --include, -i: One or more glob patterns for documentation files. Overrides --docs.
  • --strict, -s: If set, the CLI will exit with code 1 if any documentation drift is detected. Defaults to false.

Example

npx doc-sync-check src --docs docs
npx doc-sync-check src --include "docs/**/*.md" "README.md" --strict

🧠 How it Works

  1. Extraction: The parser walks your TypeScript AST and extracts exported symbols:
    • exported functions
    • exported interfaces (including property/method types)
    • exported classes and class methods (excluding private methods)
    • exported type aliases
  2. Normalization: Signatures are converted to single-line forms so multiline declarations still match docs reliably.
  3. Drift Detection: Any Markdown file mentioning a detected symbol by exact name should include the up-to-date signature. Missing or stale signatures are flagged. With --strict, drift returns exit code 1.

🤝 Contributing

We welcome community contributions! Please check out our Contributing Guide to get started on setting up the repository, running tests, and understanding the architecture.

📄 License

This project is licensed under the MIT License.