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

company-wiki-reader

v0.4.0

Published

Agent-friendly read-only lightweight Git LFS wiki synchronization

Readme

company-wiki-reader

Read-only, agent-friendly local wiki synchronization. Node.js 22+ and Git 2.39+ required (use a maintained Git release). Repository must use HTTPS; large media should be stored in Git LFS. No Git LFS client or persistent LFS media cache is required on the reader computer.

Install and update

npm install -g company-wiki-reader@latest
wiki-reader doctor --json

Git missing or not on PATH

Do not search the entire disk. doctor checks explicit WIKI_READER_GIT, managed MinGit, PATH and standard Windows installation locations with bounded probes. It reports gitPath, a version, or a structured error plus next command. Missing Git is detected before a new Wiki directory is created.

wiki-reader setup --json
wiki-reader setup --apply --json
wiki-reader doctor --json

On Windows, setup reuses usable Git, otherwise installs pinned official MinGit 2.55.0.windows.3 for the native x64/ARM64/x86 architecture in %LOCALAPPDATA%/company-wiki-reader/runtimes. No admin rights, GitHub login, global PATH modification or Git LFS client are required. --apply is mandatory to download/install. Auto source selection tries Huawei Cloud then GitHub, with fixed official SHA256 checks, 15-second idle / 120-second per-source limits and no retries beyond those two attempts. Hash/size mismatch stops installation. --source official|huawei selects one source. Archives are retained at the reported path; no unrelated files are overwritten. Downloads use direct HTTPS with TLS verification; corporate-proxy-only networks require administrator review. See the dependency branch for sources and failure handling.

On macOS setup only reports a supported package-manager installation step. Node must already be accessible to the Agent shell; this CLI cannot bootstrap the runtime needed to launch itself. Once setup/doctor passes, continue the original download/update command. There is no postinstall hook and no automatic network-access grant.

Repeat the npm install command before company updates to obtain current centrally managed connection metadata. No postinstall access, credentials or VPN configuration is installed. The owner-approved company repository address is public in this package; content and credentials are not bundled. It remains reachable only through the authorized company network/VPN.

Company employee commands

wiki-reader download --apply --json
wiki-reader update --apply --json

Both default to company-wiki in the current user's home; an optional folder argument selects a different local destination. No URL, password, CA or profile input is needed. download resumes existing managed company copies. update safely migrates recognized old endpoints and removes their local custom CA setting after backup, verifies repository history continuity and preserves local edits. Non-minimal/unknown copies require administrator review. TLS remains enabled. Only the current process bypasses proxies for the company endpoint; no global proxy, VPN or route settings change. Automatic VPN setup is not implemented.

Maintainers update src/company.mjs, retain previous endpoints in its allowlist, increment the package version and publish to latest. Installed older versions do not magically receive changed settings: employees' Agents must upgrade the package first. wiki-reader company --json exposes diagnostic metadata. Generic commands below remain available.

First download

wiki-reader init ./local-wiki --url https://git.example.org/team/wiki.git --profile minimal --apply

For an organization CA, add --ca /path/to/public-ca.crt. Obtain the URL and CA from your administrator; never disable certificate verification. Authentication-required repositories are not yet supported. Your existing network/VPN must already reach the server.

minimal includes searchable text and local attachments referenced in published Markdown notes; video, audio, archives and build-working folders are excluded. Raw text is retained but raw scraped galleries do not automatically bring every source image. Dynamic links and ambiguous wiki-style filenames are not fully resolved; review expected attachments. no-video retains all non-video files and can be larger.

Update

wiki-reader plan ./local-wiki --json
wiki-reader sync ./local-wiki --apply --json
wiki-reader status ./local-wiki --json

Local edits cause conflicts and are preserved. Remote deletions currently require review. Downloads are hash-checked; completed files can be recognized on retry. Incomplete files restart from the beginning, not HTTP byte-range resume. One temporary download is used at a time; replaced-file backups are retained locally and may require reviewed cleanup. Updates are file-by-file, not a whole-tree atomic transaction. Git object metadata is retained, so large ordinary Git blobs can still use storage: put source media in LFS.

Agents

wiki-reader skill source
wiki-reader skill install --target /path/to/agent/skills/wiki-reader --apply
wiki-reader skill status --target /path/to/agent/skills/wiki-reader

The CLI package is the single source of truth. Skill installs are links/junctions; unrelated existing skill folders are never overwritten. Use the Agent's documented skill directory. Codex and SealSeek instruction adapters are implemented, not yet clean-regression tested. Accio integration is unresolved pending its runtime contract. Any permitted terminal-capable Agent can invoke the CLI without native integration.

Scope: anonymous HTTPS read; no push, administrative changes, credentials provisioning, or general-purpose backup. Public distribution is not a grant of access to any company's wiki. The package is currently marked UNLICENSED; no open-source license grant is implied. Version 0.4.0 has automated macOS CLI and simulated Windows discovery/failure tests. Real Windows MinGit installation and clean Agent regression remain separate acceptance gates; do not infer those passes from unit tests.