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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cogs-sdk

v5.0.1

Published

Unified JavaScript SDK for Cogs' APIs

Downloads

340

Readme

A unified JavaScript SDK for the Cogs (cogswell.io) APIs

Version npm

This module contains the JavaScript SDKs for the various Cogs APIs.

  • Info - Informational APIs requiring no authentication.
  • Tools - Customer APIs which are meant for Cogs' customers' internal use only (not end-user apps, websites, or devices). These require authentication using customer API key credentials.
  • CEP - CEP APIs which are meant for client software (apps, devices, etc.). These require authentication using derived client (salt/secret pair generated by the tools API) credentials.
  • Pub/Sub - Pub/Sub APIs which are also meant for client software. These require authentication using Pub/Sub project keys.

Configuration

There are different configurations for the client and tools SDKs. While it is possible to include all key components (both the api key and client key) required in order to use both at the same time (and this is fine for testing on your own equipment), the secret component of your Cogs API key should never be placed into an app, a consumer device, or field unit.

An example of each type of config are included in this repository in the cogs-tools.json and cogs-client.json for the tools and client APIs respectively.

The tools SDK requires that the api_key.access and api_key.secret fields be populated.

The client SDK requires that the api_key.access, client_key.salt, and client_key.secret fields be populated.

API Documentation

Full Cogs API