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

grakn-api

v0.1.1

Published

Alternative grakn package to communicate in a simple way to the grakn API.

Readme

Simple GRAKN API

Alternative package for a more simple way to connect to the grakn api. It principal use case is to execute 'GRAQL' queries on the data base but you can also make GET request to different endpoints.

Prerequisites

You need to have installed GRAKN and an instance running: GRAKN website.
By default, GRAKN runs at localhost:4567 with the keyspace grakn, but you can change that. To reflect this into this app you must change these environment variables:

  • GRAKN_HOST
  • GRAKN_PORT
  • GRAKN_KEYSPACE

Or provide different values in the options argument, see options.

By default the protocol used is http (to work on localhost) but if you want to use https you should change the environment variable NODE_ENV to production or the correspondent option, see options.

Installation

npm install --save grakn-api

Usage

Is as simple as

const grakn = require('grakn-api')()
grakn.execute('match isa person has name $name; get;')
  .then(res => console.log(res)) // Do what you want with the response
  .catch(err => console.error(err)

If you want to list the available keyspaces you can run

grakn.getKeyspaces()
  .then(res => console.log(res))
  .catch(err => console.error(err))

To get something for a specific path you can run

grakn.get('/kb/path/to/something')
  .then(res => // Do something with the response)
  .catch(err => // Catch the error)

Options

When you create the grakn service you can pass it an object with options:

require('grakn-api')({
  keyspace: string, // Ex: 'grakn'
  hostname: string, // Ex: www.mygrakndatabase.com
  port: number, // Ex: 4567
  protocol: string // 'http' or 'https'
})

Or provide the defaults as environment variables.

Author

Fabián Souto Herrera
[email protected]