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

@dangerousthings/globalplatform-capfile

v0.1.0

Published

Java Card CAP file parsing and load file data block assembly

Readme

@dangerousthings/globalplatform-capfile

Reads Java Card CAP files: package AID, applet AIDs, and the component order a card expects during LOAD.

Acknowledgements

Protocol details that are easy to get subtly wrong were verified against GlobalPlatformPro and capfile — by Martin Paljak and the GlobalPlatformPro contributors — rather than guessed at. PUT KEY is the clearest case: the specification leaves the key-data cipher ambiguous enough that both readings are widely believed, and the wrong one leaves a card holding a key nobody can reproduce.

This is an independent implementation. No code is taken from either project — what was taken is the answer to "which of these two plausible things do real cards accept", which is the part no specification reliably tells you.

License

MIT