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

officejs-manifest-validator

v1.1.0

Published

Validate Office Add-in XML manifests — schema checks, resource ID integrity, type-mismatch detection, URL reachability

Readme

Office.js Manifest Validator

A CLI tool for validating Office.js XML manifests. Runs Microsoft's official schema validation, then a second static analysis pass covering things the gateway doesn't catch.

Setup

npm install office-addin-manifest fast-xml-parser node-fetch

Usage

node validate-manifest.mjs <manifest.xml> [options]

| Option | Default | Description | |---|---|---| | --timeout <ms> | 5000 | HTTP request timeout per URL | | --skip-urls | off | Skip URL reachability checks entirely | | --only-local | off | Only probe localhost / 127.x.x.x URLs | | --help | | Print usage |

Exit code 0 = clean (or warnings only), 1 = errors found — suitable for CI.

What it checks

Pass 1 — Microsoft schema validation
POSTs the manifest to validationgateway.omex.office.net, the same endpoint used by the official office-addin-manifest validate command. If the gateway is unreachable (offline, on-prem CI), this pass degrades to a warning and the static checks still run.

Pass 2 — Static analysis

| Check | Errors on | Warns on | |---|---|---| | resid integrity | resid="X" with no matching declared resource | Declared resource IDs never referenced anywhere | | Duplicate IDs | Same id= on multiple controls or groups | — | | Required fields | Missing <Id>, <Version>, <ProviderName>, <DefaultLocale>, <DisplayName>, <Description> | — | | GUID format | <Id> value that isn't a valid GUID | — | | FunctionFile | ExecuteFunction buttons with no <FunctionFile> declared, or <FunctionFile resid> pointing to unknown resource | — | | URL reachability | External URLs returning 4xx or unreachable | localhost URLs unreachable (dev server may just not be running) | | AppDomain coverage | — | External host used in resources but missing from <AppDomains> |

Notes

  • Self-signed certificates on localhost are accepted (no rejectUnauthorized).
  • URL probes use HEAD requests with a concurrency of 8.
  • Orphaned resource IDs (declared but unreferenced) are informational only — they cause no runtime issues, the Office host only resolves IDs that are actually referenced.