Example Bomly detector plugin for Bun projects. It intentionally registers PackageManagerOther and declares bun.lock, bun.lockb, and package.json as evidence patterns, which shows how a plugin can support a package manager before Bomly has a first-class SDK enum for it.
The implementation keeps the parser small for example purposes: it reads dependencies from package.json and emits npm PURLs while the detector itself is selected through the generic other package manager.
go test ./...
go build -o bin/bomly-plugin-bun-lock-detector ./cmd/bomly-plugin-bun-lock-detectorOn Windows, use bin/bomly-plugin-bun-lock-detector.exe.
bomly plugin install ./bin/bomly-plugin-bun-lock-detector --dev
bomly plugin enable bomly.examples.detector.bun-lock
bomly scan --path ./some-bun-project --detectors bomly.examples.detector.bun-lockbomly plugin install ./dist/bomly-plugin-bun-lock-detector_linux_amd64.tar.gz
bomly plugin enable bomly.examples.detector.bun-lockDirect URL installs are also supported, but they must include either a checksum or the explicit insecure opt-out:
bomly plugin install https://example.internal/bomly-plugin-bun-lock-detector_linux_amd64.tar.gz \
--checksum sha256:<digest>export BOMLY_GITHUB_TOKEN=<token-with-release-access>
bomly plugin install github:bomly-dev/bomly-plugin-bun-lock-detector@v0.1.0
bomly plugin enable bomly.examples.detector.bun-lockGITHUB_TOKEN, GH_TOKEN, and GITHUB_AUTH_TOKEN are also accepted. The token is only attached to github:owner/repo@tag release metadata, checksum, and asset downloads.