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

ai-matcher

v0.0.1

Published

Microservice that matches query strings to a large database of questions/answers, with context

Readme

ai-matcher

Microservice that matches query strings to a large database of questions/answers, with context

Setup

Clone the repo. npm install. Copy conf.json.example to conf.json. Run mongod locally in another process.

npm test to run test suite. npm test -- -w to watch for file updates. npm test -- test/route-query.js to run tests on a particular file.

npm start to spin up the server, then call make requests with

curl 'localhost:3002/api/query?question=how+are+you' -H 'Authorization: Bearer test'

Design

Endpoints

All inputs and outputs are JSON. Query parameters should be sent like so:

  • Dates in Query Strings should be in ISO_8601 format
  • Arrays in Query Strings should be any format understood by qs (a[]=b&a[]=c works fine)
  • Bools in Query Strings should be 0 or 1
  • PUT methods merged onto the existing objects using _.assign
  • created and updated are set automatically and cannot be modified

  • GET /query - Run a question through the system. Creates a Log entry.

    • Query Parameters
      • question : String - User's question
      • messagingService : String - filters the Understandings based upon the college we are concerned about
      • contexts : [String] - allows access to Understandings that have inputContexts specified
      • userId : String - For logging purposes
    • Returns
      • success : Boolean
      • topic : String - topic for the matched Understanding
      • answer : String - answer to send the user
      • outputContexts : [String] - contexts that should be sent with the next request
      • logId : String - id of the generated Log entry.
  • GET /logs - Return a list of all logs, optionally filtered. Please filter, or there will be too many results

    • Query Parameters
      • createdBefore, createdAfter, updatedBefore, updatedAfter : Date
      • needsReview, handled : Boolean
      • messagingService : String
  • PUT /logs/:id - Update a log. Sets handledDate and reviewedDate automatically

  • GET /understandings - Get a list of all understandings, optionally filtered

    • Query Parameters
      • createdBefore, createdAfter, updatedBefore, updatedAfter : Date
  • PUT /understandings/:id - Update an understanding

  • POST /understandings/ - Create a new understanding

  • GET /entities - Get a list of all entities, optionally filtered

    • Query Parameters
      • createdBefore, createdAfter, updatedBefore, updatedAfter : Date
  • PUT /entities/:id - Update an entity

  • POST /entities - Create a new entity

Collections

  • Understandings
    • created : Date
    • updated : Date
    • topic : String
    • keywords : [String]
    • outputContexts : [String]
    • questionGroups : [Object]
      • inputContexts : [String]
      • fuzzyQuestions [String]
      • exactQuestions [String]
    • answerGroups : [Object]
      • messagingService : String
      • answers : [String]
      • media : [String]
  • Entities
    • created : Date
    • updated : Date
    • name : String
    • synonymGroups : [Object]
      • messagingService : String
      • synonyms : [String]
  • Logs
    • created : Date
    • updated : Date
    • userId : String - Oli User ID
    • question : String
    • inputContexts : [String]
    • outputContexts : [String]
    • topic : String
    • messagingService : String
    • answer : String
    • sentToHuman : String
    • handled : Boolean
    • handledBy : String - Oli User ID
    • handledDate : Date - Set automatically with PUT /logs if {handled : true}
    • handledAction : [String]
    • humanResponse : String
    • reviewed : Boolean
    • reviewedBy : String - Oli User ID
    • reviewedDate : Date - Set automatically with PUT /logs if {needsReview : true -> false}
    • reviewedAction : String
    • error : String