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

nxp-originality-verifier

v0.1.0

Published

Verify NXP Originality Signature

Downloads

3

Readme

NXP Originality Verifier

Lightweight library to verify NXP Originality Signature.

Installation

$ npm install nxp-originality-verifier --save

Usage

This library assumes you already know how to work with RFID tags. It's up to the calling application to obtain and provide tag ID and originality signature to the verifier.

const OriginalityVerifier = require('nxp-originality-verifier');

const originalityVerifier = new OriginalityVerifier();

const tagId = '04ee45daa34084';
const originalitySignature = 'ebb6102bff74b087d18a57a54bc375159a04ea9bc61080b7f4a85afe1587d73b';
if (!originalityVerifier.verify(tagId, originalitySignature)) {
  throw new Error('Failed to verify originality signature');
}

By default the verifier checks against all known public keys. If that is not what you want, you can use a subset of known keys, or even your own keys (well I guess that would be your tags' manufacturer keys).

const originalityVerifier = new OriginalityVerifier([
  '04494e1a386d3d3cfe3dc10e5de68a499b1c202db5b132393e89ed19fe5be8bc61',
  '0490933bdcd6e99b4e255e3da55389a827564e11718e017292faf23226a96614b8',
]);

Known public keys

NXP

The widely known 04494e1a386d3d3cfe3dc10e5de68a499b1c202db5b132393e89ed19fe5be8bc61 key works for MIFARE UL and NTAG. The 0490933bdcd6e99b4e255e3da55389a827564e11718e017292faf23226a96614b8 key is for MIFARE UL EV1. I don't have access to other tag families, so if you can verify keys against other tag families, please open an issue and let me know about your findings. The keys are from NXP TagInfo.

Mikron

The 04f971eda742a4a80d32dcf6a814a707cc3dc396d35902f72929fdcd698b3468f2 key is for tags made by Mikron. As far as I know they don't sign their tags unless specifically requested. In this case the READ_SIG command returns all zeros.

License

MIT