@ottimis/mqtt-browser
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
ottimisgroupgbettomariana261308gigicenedaedoardo.croceottimis-oneottimis-two
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is inside mqtt.js WebSocket transport code, not malicious — it's part of the bundled mqtt library. | ai | |
| phantom-deps | phantom-dep:mqtt | AI (phantom-deps): Package is a browserify bundle of mqtt; the dependency is consumed at build time, not via import statements. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.2.9 | 1 / 1 |
v4.2.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.