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

openproct

v0.0.1

Published

OpenProct is an open-source framework for adding proctoring features to any website.

Readme

OpenProct

OpenProct is an open-source framework for adding proctoring features to any website. The core design centers around a single handler function at an API route, paired with a simple configuration in lib/proctor.ts. This approach aims to make it easy for web developers and LLMs to integrate proctoring logic in a consistent, scalable way.

Vision

  • Provide a unified, handler-based API that websites can plug into to enable proctoring functionality.
  • Use a configuration file (lib/proctor.ts) to define proctoring behavior and integrate different applications.
  • Grow into a library of numerous proctoring logics contributed by the community via PRs.
  • Offer practical tools like clipboard blocking, monitoring, banning, and more.

Core Concepts

  • Handler-based API route: Your application sets up a single API route that delegates to OpenProct’s handler function. This route becomes the entry point for proctoring events and checks.
  • lib/proctor.ts: A configuration module where you define:
    • What applications are being proctored (e.g., coding, QnA, mechanical design).
    • Which tools are enabled (e.g., clipboard blocking, monitoring, banning).
    • Any custom logic or integration points needed for a specific application.

Integrations

OpenProct is designed to make it straightforward to integrate proctoring for various application types, including but not limited to:

  • Coding environments
  • QnA systems
  • Mechanical design tools

Each integration can define its own proctoring logic, all managed through a centralized configuration.

Tools

OpenProct intends to offer a set of tools that can be enabled per integration:

  • Clipboard blocking
  • Monitoring and activity tracking
  • Banning and enforcement mechanisms

These can be toggled and configured through lib/proctor.ts.

Community-Driven Growth

OpenProct’s library of proctoring integrations is meant to grow through community contributions:

  • Add new integrations via PRs for different applications.
  • Extend proctoring logic and tools in a modular fashion.
  • Help build a broad ecosystem that web developers and LLMs can easily adopt.

Getting Started (Conceptual)

  1. Create an API route in your app and attach the OpenProct handler function.
  2. Add a lib/proctor.ts configuration file to define:
    • Your enabled integrations (e.g., coding, QnA, mechanical design).
    • The tools you want to apply (clipboard blocking, monitoring, banning).
  3. Implement or select proctoring logic for your target application(s) and wire it up in lib/proctor.ts.

Contributing

Contributions are welcome. You can:

  • Propose new integrations for different application types.
  • Improve existing proctoring logic.
  • Extend the toolkit with additional monitoring or enforcement features.

Please open a PR describing the new proctoring logic or tools and how they’re configured via lib/proctor.ts.

License

MIT