bonjour
A Bonjour/Zeroconf implementation in pure JavaScript
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Historical transition (2015) from balderdashy to watson (Thomas Watson Steen), a prolific trusted npm author. New deps are watson's own mDNS libraries; this is a legitimate rewrite, not a hijack. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): watson is a well-established npm publisher with 759 approved packages; addition is part of the documented 2015 ownership transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): balderdashy removal is part of the legitimate 2015 handoff; no evidence of compromise. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to watson is a known, legitimate 2015 transition; watson's identity and repo URL are consistent across all metadata. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects a full rewrite from a Sails.js app bundle to a lean mDNS library; expected and benign. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (multicast-dns, mdns-txt, multicast-dns-service-types) are watson's own well-known mDNS libraries, core to the rewritten Bonjour implementation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.5.1 | 6 / 3 | |
| 3.5.0 | 6 / 3 | |
| 3.4.0 | 6 / 3 | |
| 3.3.1 | 5 / 3 | |
| 3.3.0 | 5 / 3 | |
| 3.2.2 | 5 / 3 | |
| 3.2.1 | 5 / 3 | |
| 3.2.0 | 4 / 3 | |
| 3.1.0 | 4 / 3 | |
| 3.0.1 | 4 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.0.0 | 3 / 2 | |
| 1.0.0 | 6 / 0 |
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsAll previous maintainers (balderdashy) were replaced by new maintainers (watson). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-12-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.