gradejs VS nexe

That's weird. Could you please provide more details and submit an issue? https://github.com/gradejs/gradejs/issues

I’d like to share an open source project I’ve been working on during the last year. It analyzes production JavaScript code and detects bundled NPM package versions. A vulnerability is shown when a specific detected version contains known vulnerabilities, taken from the Github advisory.

There’s also a dedicated package page, that shows accumulated statistics of a package. It’s like wappalyzer or builtwith but with better accuracy. For example: https://gradejs.com/package/react

So far I’ve only indexed ~10,000 popular websites. The current version works for Webpack bundles with 70-90% accuracy and ~3% false positive. The package detection algorithm is designed to match minified and tree-shaken AST subtrees for each export per bundled JS module.

I'd like to collect any feedback from the community.

Repository: https://github.com/gradejs/gradejs

Source code: https://github.com/gradejs/gradejs

Well, the accuracy question is tricky, since there are two problems. A false positive mistake is a tool showing something that IS NOT bundled. A false negative mistake would be a tool NOT showing something that IS bundled. Currently we see ~30% FN and ~5% FP for GradeJS accuracy. More info.

Try it out: gradejs.com

Source code: https://github.com/gradejs/gradejs

Link: gradejs.com Source code: github.com/gradejs/gradejs

In addition to the other responses, there are node packages like pkg and nexe that you can use to package the node executable and your code into a single executable.

well... you need the code on the server in some way in order to run it. Nodejs doesn't compile to a binary. There are ways to wrap a node install and the code into a binary. But I have never used that in production and can't actually recommend it.

yes, you can even compile your js if you want a single executable, with things like nexe

https://github.com/nexe/nexe is another.