dunder-proto 1.0.0
Allow
npmjs.com
Nothing PkgFire checks stopped this release.·Checked 4 hours ago·Published 6 December 2024
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- None, and no earlier version had any
Licence and upkeep
- Licence
- MIT
- Source
- github.com/es-shims/dunder-proto ↗
- OpenSSF Scorecard
- None published for this repository, which is common for small projects and not the same as scoring badly
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.