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 🙏

© 2025 – Pkg Stats / Ryan Hefner

dpevalidator

v1.3.4

Published

A Javascript library to validate a DPE

Readme

DPE Validator

This Javascript library provide some utilities to valide a DPE

| Statements | Branches | Functions | Lines | | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Statements | Branches | Functions | Lines |

Why ?

  • Many DPEs do not always contain all the information necessary to establish scores and calculate losses for the affected housing units.
  • Before being able to carry out processing on the data, it is often necessary to be able to detect potential anomalies or missing data
  • 2 error levels will be reported:
    • warning for non-blocking errors allowing all or part of the DPE to be analyzed
    • error for blocking errors in data analysis (for example if no walls are present)
  • 2 versions of the same DPEs can be analyzed in order to detect anomalies by comparing the data (for example window number which changes between the 2 versions)

How to use it

  • npm install dpe-validator --save
  • A dpe can nom be analyzed based on its json :
import { DpeValidator } from 'dpe-validator';

new DpeValidator().validate({
    numero_dpe: "2344E0308327N",
    statut: "ACTIF",
    administratif: {...},
    ...
});
[
  {
    "code": "NO_MURS_COLLECTION",
    "level": "WARNING"
  }
]
  • Two dpe can be compared analyzed based on their json :
import { DpeComparator } from 'dpe-comparator';

new DpeComparator().compare(
  {
    mur_collection: [{}, {}],
    logement: {
      caracteristique_generale: {
        annee_construction: 1948
      }
    }
  },
  {
    mur_collection: [{}],
    logement: {
      caracteristique_generale: {
        annee_construction: 1970
      }
    }
  }
);
{
  "size": {
    "mur_collection": { "is": 2, "was": 1 }
  },
  "values": {
    "annee_construction": {
      "is": 1948,
      "was": 1970
    }
  }
}

Getting started

  • npm install to get node dependencies
  • npm run build to build the application

Tests

Unit tests

  • npm run test to start Jest tests with coverage
  • HTML and coverage reports are generated under the coverage and coverage/lcov-report folders.

Code quality

npm run qa:lint. Will check your code based on eslint.confi.js config file