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

@visin/backend-core

v0.1.7

Published

Shared backend functionality for Visin services

Downloads

1,196

Readme

@visin/backend-core

Shared backend functionality for Visin services: JWT auth middleware, inter-service auth, a centralized error handler, structured logging, and security headers/rate limiting — extracted from the near-identical copies that used to live in auth-service, group-service, vision-service, and file-service.

Installation

npm install @visin/backend-core

Usage

import express from 'express';
import {
  authenticateToken,
  optionalAuth,
  errorHandler,
  requestLogger,
  securityHeaders,
  standardRateLimiter,
  logger
} from '@visin/backend-core';

const app = express();

app.use(securityHeaders);
app.use(requestLogger);
app.use(standardRateLimiter);

// Public read, works for anonymous + logged-in users
app.get('/projects', optionalAuth, getProjects);

// Requires a valid, signed-in caller
app.post('/projects', authenticateToken, createProject);

// Must be mounted last
app.use(errorHandler);

logger.info('Service started');

Inter-service calls

import { requireInternalServiceToken, validateInternalServiceToken, allowUserOrInternalService } from '@visin/backend-core';

// Route only ever called by other services
router.post('/internal/sync', requireInternalServiceToken, syncHandler);

// Route callable by an end user OR another service
router.get('/groups/:id', validateInternalServiceToken, authenticateToken /* or optionalAuth */, allowUserOrInternalService, getGroup);

Throwing typed errors

import { NotFoundError, asyncHandler } from '@visin/backend-core';

router.get('/projects/:id', asyncHandler(async (req, res) => {
  const project = await Project.findById(req.params.id);
  if (!project) throw new NotFoundError('Project not found');
  res.json({ success: true, data: project });
}));

Required environment variables

  • JWT_SECRET — used by authenticateToken/optionalAuth to verify tokens issued by auth-service.
  • INTERNAL_SERVICE_TOKEN — shared secret for requireInternalServiceToken / validateInternalServiceToken.

Consuming this package in a standalone Docker build

Each service's Dockerfile builds from its own directory in isolation, so a workspace dependency on @visin/backend-core needs to be resolvable inside that build context — either by publishing this package to npm first and installing it normally, or by adjusting the build context / adding a copy step so node_modules/@visin/backend-core is populated before npm ci. Not yet wired up; see the repo's TODO.md.