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

circles-npm

v1.0.6

Published

circle module to use circles-api

Downloads

8

Readme

circles-npm

Node sdk for https://github.com/linnovate/circles

Overview

The circles npm provides several features that work together with the circles api to provide
organizational context to users and to enforce compermentalization of data (the ability to seclude permissions between types of users). When you use circles you can "sign" the data with it's appropriate circle (which represents who can consume it). A user can pull his "Circles" which basically communicate to what groups he belongs and what type of data can he consume. The circles npm provides

  • The function to "sign" an object with it's circles
  • The express middleware to add to your routes so they will allow or disallow access to content based on the circles signed on the content and sent to the api query.
  • Access and helper functions to the circles api (getCircles, )

Configuration

Your app should reference a circlesApi instance and should have an (express style) config setting for circles api...

circles: {
    uri: 'http://localhost:3005'
  },

the circleSettings configuration could typically be set like this...

'use strict';

module.exports = {
	displayAllSources: false,
	displayAllC19nGroups: false,
	displayAllGroups: false,
	circleTypes: {
		c19n: {
			requiredAllowed: true,
			max: 1,
			sources: true
		},
		c19nGroups1: {
			requiredAllowed: true,
			max: 1,
			requires: ['c19n']
		},
		c19nGroups2: {
			requiredAllowed: true,
			max: 1,
			requires: ['c19n']
		},
		personal: {
			requiredAllowed: false,
			max: 50,
			watchers: true
		}
	},
	cacheTime: 5,
	cacheDb: 'mongoose'
};

Usage

var circles = require('circles-npm')(app, config.circles.uri, circleSettings);

Signing data

circlesAcl.sign('mongoose', entity.sources, entity.circles, acl, function(error, circles) {}

Middleware

app.route('/api/:entity(tasks|discussions|projects|users|circles)*').all(circles.acl());