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

graphql-is-authenticated

v1.0.3

Published

GraphQL directive for checking if user is authenticated

Readme

A handy-dandy GraphQL directive for setting authentication requirement on fields.

Install

yarn add graphql-is-authenticated

Usage

You want to include @isAuthenticated directive on fields you wish to be restricted.

type Query {
    teapot: String! @isAuthenticated
}

This will return an AuthenticationError for users who are attempting to access this field, but are not authenticated.

You have two ways to specify if a user is authenticated:

Option 1: Set isAuthenticated on context

You would define it as follows for Apollo Server or similar:

import { 
    createIsAuthenticatedDirective,
    createIsAuthenticatedTypeDef
} from 'graphql-is-authenticated';

new ApolloServer({
    typeDefs: [createIsAuthenticatedTypeDef(), ...otherTypeDefs],
    schemaDirectives: {
        isAuthenticated: createIsAuthenticatedDirective()
    },
    context: (ctx) => {
        const isAuthenticated = checkIsUserAuthenticated();

        return { isAuthenticated };
    }
    ...
});

Option 2: Pass checkIsUserAuthenticated method

You can also pass a function as an argument to createIsAuthenticatedDirective which takes an argument of context, and returns a promise which resolves a boolean.

import { 
    createIsAuthenticatedDirective,
    createIsAuthenticatedTypeDef
} from 'graphql-is-authenticated';

const checkIsUserAuthenticated = async (ctx) => {
    const { req } = ctx;
    const { authorization } = ctx.headers;

    if (!authorization) {
        return false;
    }

    const isAuthenticated = await verifyAuthorizationHeader(authorization);

    return isAuthenticated;
};

new ApolloServer({
    typeDefs: [createIsAuthenticatedTypeDef(), ...otherTypeDefs],
    schemaDirectives: {
        isAuthenticated: createIsAuthenticatedDirective(checkIsUserAuthenticated)
    }
    ...
});

Supporters

Many thanks to the people below for supporting this project! 🎉

Stargazers repo roster for @Tomburgs/graphql-is-authenticated Forkers repo roster for @Tomburgs/graphql-is-authenticated