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

@vigilo/core

v0.1.1

Published

Vigilo core: detecção de ataques, mascaramento e envio de eventos.

Readme

@vigilo/core

Núcleo da Vigilo: detecção de ataques, estado por IP, camada RASP, mascaramento e envio dos eventos para a plataforma.

Para usar na sua API, instale o adapter do seu framework, que já traz o core:

| Framework | Pacote | | --- | --- | | Express 4 e 5 | @vigilo/express | | Fastify 5 | @vigilo/fastify | | node:http | @vigilo/http |

Uso direto

Para outro framework, use o cliente do core. Ele nunca lança exceção (fail-open):

import { createVigilo } from '@vigilo/core';

const vigilo = createVigilo({ apiKey: process.env.VIGILO_KEY, mode: 'monitor' });

// a cada requisição, antes do handler
const request = { method, route: '/users/:id', path, query, headers, body, ip };
const decision = vigilo.inspect(request);
if (decision.block) { /* responda 403 */ }

// depois da resposta
vigilo.record(request, { status, durationMs, decision });

route deve ser o padrão da rota, nunca o path concreto: ele vai para a plataforma sem mascaramento. Se o framework não informar o padrão, use normalizeRoutePath(path).

O formato dos eventos está no contrato de eventos, e o JSON Schema vai junto no pacote, em schemas/. As opções e garantias estão no README principal.

Licença

Apache 2.0.