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

@adze/security-validator

v1.0.0

Published

This project is a plugin for the Adze logging library to provide tools for ensuring proper context is applied to logs that are meant to record security events such as access events and authentication events.

Downloads

3

Readme

Adze Security Validator

This project is a plugin for the Adze logging library to provide tools for ensuring proper context is applied to logs that are meant to record security events such as access events and authentication events.

This library exposes some opinionated interfaces and a log listener factory for validating your security event logs.

Installation

Yarn

yarn add @adze/security-validator

npm

npm install --save @adze/security-validator

Explanation

When creating web systems it is important for security audits to log access and authentication events with the proper context attached. If a security breach has occurred and our access and authentication logs either do not exist or are missing some of their context this can hinder the recovery process as well as tracking down how the attacker compromised the system in the first place.

This library exposes an Adze log listener factory that wraps a log listener and validates that the context attached to it meets the minimum requirements. For TypeScript development environments this library also exposes some useful interfaces that can assist you with applying the proper context to your logs.

The library also exposes some type guard functions to validate if access event or authentication event meta is attached to your log context.

Security Event Context

When logging a security event, such as an access event or an authentication event, proper context is needed to ensure that the most value is created by your log. Here are the properties required by the Adze Security Validator plugin and an explanation of each.

Access Event Context

  • userId - Unique identifier of the user accessing the object.
  • subject - Service identifier or principal name that uniquely identifies the subject accessing the object.
  • description - Unique object identifier or complete description of the object AND the action requested.
  • hostname - The hostname of the entity accessing the object.
  • context - Optional authorization context details.

Authentication Event Context

  • userId - Unique identifier of the user accessing the object.
  • mechanism - The authentication mechanism used.
  • subject - Service identifier or principal name that uniquely identifies the subject accessing the object.
  • description - Unique object identifier or complete description of the object AND the action requested.
  • hostname - The hostname of the entity accessing the object.

Tutorials

API Documentation