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

regen_1_scoring

v0.1.0

Published

Script that will translate Regen 1's scoring criteria to be automatically applied to farmer data.

Readme

Regen1 Scoring

Resources

Getting all required inputs

Populate the .env file.

  • Get a baserow token for our tables, store it under the BASEROW_TOKEN key.

Retrieve the baserow tables

  • Use the node script ./scripts/getBaserowScoring.js. It will store the scoring table under ./input_data/parsed_scoring_table.json.

Add the SurveyStack survey description

  • You can download it from survey stack, if you click on the edit menu.
  • The baserow tables are parsed starting from this definition, using another script, parseSurveyDescriptionFile.js, which outputs data dictionaries that are the base for the Baserow Scoring tables. This is not required to apply scores, as the Baserow Scoring tables are an input.
  • It should be ./input_data/current_survey_definition.json.

How to test the Functions

Library tests

  • You will find abundant, detailed and well structured examples in the tests.
  • Some functions_walktrough scripts also toy with different components and might help inspect and get acquainted if needed.

Example of how to use in a server

  • functions_walktrough/example_server_call.js.

Main Filosophy

  • First, you will obtain parsers, by feeding the Scoring Table to adequate classes. There are functions provided by the library simplifying the process, and one that encompasses the whole process, parametrizeWholeScoringProcess the only argument taken is the scoring table.

  • Parsers have a score method, that will output a score and information explaining how it was assigned when fed with a survey submission.

Scoring Steps

  • Questions search for adequate data, compare it with known values and also gather what's needed for modifications to the score, such as verification.
  • Subsections are composed of many questions, they will evaluate their included questions, obtain partial scores, modify them and generate a subsection score.
  • Sections are componsed of subsections.
  • A Scoring describes the whole process, and will score a full survey submission.
  • Every level will also provide data from the deeper ones.