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

@creative-realities/role-provider-client

v2.0.0

Published

A node package for signing Role Prover requests.

Readme

Role Provider Client

A node package for signing Role Prover requests.

Example setup

It would be better to pull configuration data from a config file. But for example:

var roleProviderConfig = {
	service_name: "My Service",
	service_id: "507f1f77bcf86cd799439011",
	secret_key: "188bc580-8e50-11e5-8994-feff819cdc9f",
	role_provider_host: "roles.dev.reflect.systems" // Optional. Defaults to "roles.reflect.systems"
};
var roleProviderClient = require("role-provider-client")(roleProviderConfig);

Example usage

var method = "POST";
var uri = "/api/users";
var authHeader = roleProviderClient.getAuthHeader(method, uri, req.session.token);

Optional app

Loading api with express app.

  • The app is assumed to have session middleware.
  • The app is assumed to have a body parser.
roleProviderClient.loadAPI(app);

Other config options:

var roleProviderConfig = {
	// ...
	roleProviderApiRoute: "/api/stuff", // defaults to "/api/roles"
	loginRoute: "/login-stuff" // defaults to "/login"
};

It is up to you to implement the login page at the loginRoute, which should load an iframe from the role provider server. Example is in the ad-server-front repository. It is also up to you to implement the client side portion of the API that this package provides.

Auth middleware

app.use(roleProviderClient.authMiddleware);

The authMiddleware whitelist is an optional object whose keys are routes, and values maybe be arrays of actions or simply "*" to whitelist all actions or to whitelist a route that doesn't use actions. The loginRoute will default to "*". The whitelisted routes and actions will pass through the authMiddleware without requiring an authenticated session user.

roleProviderConfig.middlewareWhitelist = {
	"/api/public": "*",
	"/api/semi-public": ["getPublic", "doFunStuff"]
};
var roleProviderClient = require("role-provider-client")(app, roleProviderConfig);

Callbacks

var route = "/account";
var action = "getAccount";
roleProviderClient.on(route, action, function(data, next) {
	// If response body was JSON, data will be an object.  Otherwise it is a String.
	...
	// In case of an error
	if (error)
		return next({status: 404, message: "Error message"});
	...
	// success
	next();
});