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

ssol-rest

v1.0.3

Published

REST API wrapper for the bloody SSOL

Readme

ssol-rest

REST API wrapper for SSOL

Test it out at http://immense-anchorage-9037.herokuapp.com

Quick Start

Get yourself a sessionToken first by sending a POST request to

localhost:5000/auth/login

with the parameters

{
    username: YOURUNI,
    password: YOURPASSWORD
}

It should return something like this

{"sessionToken":"rAnDoMtOkEn"}

Then use the one of the method we have so far

localhost:5000academic/schedule?sessionToken=rAnDoMtOkEn

which should return you a list of courses you're currently taking for the term

[{
    "dept": " COMS",
    "courseCode": "W3261",
    "section": "001",
    "fullName": "COMPUTER SCIENCE THEORY",
    "grading": "3.00",
    "instructorName": "Alfred Aho",
    "instructorEmail": "[email protected]",
    "day": ["Mo", "We"],
    "time": "1:10pm-2:25pm",
    "room": "833",
    "building": "MUDD",
    "startDate": "09/02/14",
    "endDate": "12/08/14"
}, {
    "dept": " COMS",
    "courseCode": "W4111",
    "section": "001",
    "fullName": "INTRODUCTION TO DATABASES",
    "grading": "3.00",
    "instructorName": "Alexandros Biliris",
    "instructorEmail": "[email protected]",
    "day": ["Tu"],
    "time": "1:10pm-3:40pm",
    "room": "RTBA",
    "building": "",
    "startDate": "09/02/14",
    "endDate": "12/08/14"
}]

Methods

Auth

POST auth/login

Parameters:

  • username: User's UNI
  • password: User's password

Output:

  • sessionToken: User's session token

Academic

GET academic/schedule

Parameters:

  • sessionToken: User's session token obtained from login

Output:

  • Array of classes

GET academic/search_class

Parameters:

  • sessionToken: User's session token obtained from login
  • keyword: Search keyword
  • term: The term to search in. 2014 Fall will be 20143, 2014 Spring will be 20141 and so on.
  • page (optional): Which page to start on. Must be used simultaneously with offset
  • offset: some stupid number to keep CUIT's linked list in check.

Output:

  • Array of classes
  • currentPage: current page
  • nextPage: the number to put in the next REST request for the next page of results. If this is 0, this means there's no next page.
  • offset: the number to put in the next REST request as well. Just chuck it in. If 0, no next page.

Disclaimer

I really need to authenticate using HTTPS. I whacked this out in an afternoon. Don't blame me. I'm getting sleepy. Goodnight.