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

opencode-office

v0.1.17

Published

Microsoft Office plugin for OpenCode

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

al-scional-scion

Keywords

Readme

opencode-office

Microsoft Office Plugin for OpenCode.

Features

  • 🏗️ TypeScript-based module architecture
  • ⚡ Biome for high-performance linting and formatting
  • 📦 Bun/npm build tooling
  • 🧪 Vitest testing setup
  • 🚀 GitHub Actions CI/CD with Trusted Publishing (OIDC)
  • 📝 Automated releases with Release Please

Getting Started

  1. Install dependencies:

    bun install

  2. Development:

    • npm run build - Build the module
    • npm run lint - Lint code
    • npm run format - Format code
    • npm run test - Run tests

Releasing & Publishing

This project uses Release Please for automated versioning and changelogs.

1. Conventional Commits

We follow the Conventional Commits specification for all changes:

  • fix: bumps patch version (0.1.0 -> 0.1.1)
  • feat: bumps minor version (0.1.0 -> 0.2.0)
  • feat!: or fix!: bumps major version (breaking changes)

2. Automated Release Workflow

  1. Push your commits to the main branch.
  2. Release Please will automatically open/update a "Release PR" with the new version and changelog.
  3. Merge the Release PR to trigger the automated build and publish to npm.

3. NPM Trusted Publishing

Authentication with npm is handled automatically via GitHub Actions OIDC (OpenID Connect). No manual tokens are required.

Author

License

MIT License. See the LICENSE file for details.