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

lpm-web

v1.0.0

Published

Este server tiene los siguientes requerimientos.

Downloads

68

Readme

lpm

Este server tiene los siguientes requerimientos.

crear usuarios anonimos

Un usuario puede subir paquetes, también puede eliminar paquetes propios siempre que no sea utilizado por otro usuario.

Un usuario también puede crear tokens con ciertos permisos para compartir.

Subir paquetes:

  • publicos/privados
  • cifrados/descifrados

El request debe darme

  • headers: [autentiation-cookie{string}] °
  • url_params: [nombre_version{string}] [private{boolean|undefined}] [cipher{string|undefined}] ° Solo el user tiene acceso al paquete si está marcado como private, si no lo está no nesecitarás ninguna cookie para instalar el paquete.

Si se manda una clave a chiphred el paquete se cifrará utilizando la clave enviada por la url. Si no, se guardará directamente.

El header con la cookie es obligatorio, ya que se nesecita conocer el usuario.

Descargar paquetes

  • headers: [autentiation-cookie{string|undefined}] °
  • url_params: [nombre_version{string}] (si no se da versión se buscará el latest) [token{string|undefined}] [decipher{string|undefined}] °

Eliminar paquetes

  • headers: [autentiation-cookie{string|undefined}] °
  • [nombre{string}] [token{string|undefined}] °

Esto es maravilloso y da un buen roadmap para el futuro... por ahora solo será para mí y con una autenticación en duro solo para mi

como usar por ahora.

endpoints

GET /pkg/:[name]?decipher="mi clave decifradora"&lpm-session="mi cookie de sesión"

POST /publish?lpm-session="mi cookie de sesión" body:{name, version} headers: {
type : 'multipart/form-data' cipher : 'mi clave de cifrado o undefined' }, body : data (el paquete)