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

lsos

v0.2.1

Published

:information_source: This readme is meant for developers of open source projects who want to integrate the Lsos. Users of Lsos projects can get more infos at [lsos.org](https://lsos.org).

Downloads

22

Readme

Lsos Library for JavaScript

:information_source: This readme is meant for developers of open source projects who want to integrate the Lsos. Users of Lsos projects can get more infos at lsos.org.

See Lsos - FAQ - What does the Lsos library do? for an overview of what the Lsos libray does.

Usage

import { verify } from "lsos"; // npm install lsos

verify({
  // Your project's name
  projectName: "My Open Source Project", // Required

  // Your npm package that calls this `verify()` function
  npm: "my-open-source-project", // Required

  // Only require an activation key when your user's repository had
  // `minNumberOfAuthors` Git authors in the last 3 months.
  minNumberOfAuthors: 3, // Optional (default value: 3)

  // Never block users, show a `console.warn` instead.
  trustMode: false, // Optional (default value: false)

  // Free trial
  freeTrialDays: 31, // Optional (default value: 31)
});

If your user needs an activation key but doesn't have one then verify() throws an error blocking your user from using your code.

Your user doesn't need an activation key if:

  • Your user's repository had less than minNumberOfAuthors Git authors in the last 3 months. (We consider a repository with only few authors a small project; Lsos projects are free for small projects.)
  • Your user's repository is public. (This means that your project can be developed and contributed to without activation key.)
  • The free trial didn't end. (A console.info is shown to your user letting him know that he is using the free trial.)
  • The trustMode option is set to true.

verify() (and the Lsos in general) has no effects in these situations.

All checks are done by calling Git commands in the postinstall step. Other than Git commands, nothing external to the lsos code is executed and no network calls are made. The verify function has no dependencies and is isomorphic; the lsos package can be used for Node.js libraries as well as browser libraries.