@usebruno/js 0.55.0
PkgFire would install this release with a warning.·Checked 39 minutes ago·Published 22 October 2026
Why
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Detects base64 decoding followed by code execution
-
warnSuspicious behaviour
Newly added dependency @usebruno/requests@0.22.0 is suspicious (risk score 6.5/10). Matched rules: threat-filesystem-read, threat-network-exfiltration, threat-runtime-environment-read, threat-runtime-obfuscation-base64exec, threat-runtime-obfuscation-unicode. It was introduced in @usebruno/js@0.55.0 and was not a dependency of the previous version 0.54.0.
-
warnSuspicious behaviour
1 new behaviour since 0.54.0
-
warnNew publisher
Published by "sid-bruno", an account that shipped none of this package's earlier versions. A trusted name released by an unfamiliar account is what a stolen maintainer account looks like from the outside. It can equally be a handover - check the release.
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
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.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
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.