diff --git a/README.md b/README.md index b764ab37..db88662c 100644 --- a/README.md +++ b/README.md @@ -148,7 +148,7 @@ bomly scan --json # SARIF for security tabs and code-scanning integrations bomly scan --enrich --audit --fail-on high --format sarif -# Write SBOMs while still showing the normal report +# Write SBOM artifacts (add --format text to also print the report) bomly scan -o spdx=sbom.spdx.json -o cyclonedx=sbom.cdx.json # Emit one SBOM to stdout diff --git a/docs/AUDITORS.md b/docs/AUDITORS.md index d33c51a8..cb62dc31 100644 --- a/docs/AUDITORS.md +++ b/docs/AUDITORS.md @@ -20,7 +20,7 @@ network. | [`license`](auditors/license.md) | Package licenses vs. allow/deny SPDX policy | `--allow-license`, `--deny-license`, `--license-exempt-package` | | [`package`](auditors/package.md) | Denied packages, typosquatted names, and source changes | `--deny-package`, `--deny-group`, `--protected-package`, `--typosquat-threshold`, `--typosquat-mode`, `--fail-on source-change` | -Select a subset with the `--auditors` selector (e.g. `--auditors license`). See the [per-auditor reference](auditors/) for options, examples, and limitations. Auditors are also a plugin extension point — for a worked example of an external auditor, see the [Meme Dependency Auditor](https://github.com/bomly-dev/bomly-plugin-meme-auditor). +Select a subset with the `--auditors` [selector](COMMANDS.md#selector-grammar) (e.g. `--auditors license`). See the [per-auditor reference](auditors/) for options, examples, and limitations. Auditors are also a plugin extension point — for a worked example of an external auditor, see the [Meme Dependency Auditor](https://github.com/bomly-dev/bomly-plugin-meme-auditor). ## When auditors run diff --git a/docs/COMMANDS.md b/docs/COMMANDS.md index 777a40c0..079d24e2 100644 --- a/docs/COMMANDS.md +++ b/docs/COMMANDS.md @@ -12,8 +12,21 @@ Everything Bomly does runs through one of these commands. The three graph comman | `bomly mcp` | Serve Bomly's tools to MCP-aware AI agents | [MCP Server](MCP.md) | | `bomly version` | Print version information | — | +## Shared option surface + The three graph commands share one option surface: the same target flags (`--path`, `--recursive`, `--url`/`--ref`, `--image`, `--sbom`), the same pipeline gates (`--enrich`, `--audit`, `--analyze`), the same component selectors (`--detectors`, `--matchers`, `--auditors`, `--analyzers`), and the same output flags (`--format`, `-o`, `--json`). Learn them once on the [scan](commands/scan.md) page; the [explain](commands/explain.md) and [diff](commands/diff.md) pages cover only what differs. -Selectors use one grammar everywhere: a bare list replaces the default set (`--matchers osv`), `+name` appends to the defaults, and `-name` removes from them (`--matchers -depsdev-license-matcher`). Output targets use `-o ` or `-o =`, repeatable for multiple artifacts in one run. +## Selector grammar + +`--detectors`, `--matchers`, `--auditors`, `--analyzers`, and `--ecosystems` all accept the same selector list: + +- A bare list **replaces** the default set: `--matchers osv` runs only OSV. +- `+name` **appends** to the defaults: `--matchers +clearlydefined-license-matcher` adds an installed plugin matcher. +- `-name` **removes** from the defaults: `--matchers -depsdev-license-matcher` keeps everything else. +- Entries are comma-separated and may mix forms: `--ecosystems +go,-npm`. + +A name must belong to a registered component — a typo or a plugin that isn't installed fails with exit `4` and a message naming the unknown selector. Discover valid names with `bomly plugins list`. + +Output targets use a separate spec: `-o ` or `-o =`, repeatable for multiple artifacts in one run — see [Output Formats](OUTPUT_FORMATS.md#additional-output--o). For every flag with its config key, environment variable, and default, see the generated [Config Reference](CONFIG_REFERENCE.md) — or run `bomly --help`. diff --git a/docs/DETECTORS.md b/docs/DETECTORS.md index 103cd252..a0d015af 100644 --- a/docs/DETECTORS.md +++ b/docs/DETECTORS.md @@ -40,7 +40,7 @@ Bomly prefers native detectors because they preserve edges (needed by `bomly exp ## Selecting detectors -Use `--detectors` to restrict or extend the default set with the standard `+/-` selector grammar: +Use `--detectors` to restrict or extend the default set with the standard [selector grammar](COMMANDS.md#selector-grammar): ```bash # Use only the native Go detector diff --git a/docs/GETTING_STARTED.md b/docs/GETTING_STARTED.md index 75eac6be..6ba4cf06 100644 --- a/docs/GETTING_STARTED.md +++ b/docs/GETTING_STARTED.md @@ -32,6 +32,18 @@ This runs the default pipeline: 2. Run the best detector chain for each subproject. 3. Render a human-readable report. +On a small npm project it looks like this: + +```text +✓ 68 packages in 1 manifest (1 direct, 67 transitive · runtime 68, dev 0) + +Top-level dependencies + NAME VERSION LICENSE SCOPE VULNS + express 4.19.2 MIT runtime - +``` + +The VULNS column stays empty until you enrich — that's the next section. + **Matchers are offline by default** — no `--enrich` means zero outbound enrichment calls. **Detectors** may still invoke their build tool (Go, Maven, Gradle, sbt) which can download packages from package registries. Lockfile-parser detectors (npm, pnpm, yarn, Composer, Bundler, NuGet, GitHub Actions) and SBOM ingest are fully offline. See [Detectors → Network behavior](DETECTORS.md#network-behavior) for the full breakdown. Pass `--path` to scan a directory other than the current one: @@ -68,6 +80,21 @@ See [Scan targets](SCAN_TARGETS.md) for the full target list. bomly scan --enrich ``` +The same project now shows which packages carry advisories and whether fixes exist: + +```text +✓ 68 packages in 1 manifest (1 direct, 67 transitive · runtime 68, dev 0) + +✓ Enriched via Grype, deps.dev License Matcher + +✓ 7 fix suggestions for 7 of 7 vulnerable packages. + Run again with --format json to see remediation details. + +Top-level dependencies + NAME VERSION LICENSE SCOPE VULNS + express 4.19.2 MIT runtime 1L +``` + This calls the enabled built-in matchers, including OSV, KEV, deps.dev, and OpenSSF Scorecard when selected. Responses are cached under `~/.bomly/cache/`. See [Matchers](MATCHERS.md) for the per-source list and cache TTLs. ClearlyDefined license and endoflife.date lifecycle enrichment are available as external matcher plugins. ## Generate an SBOM @@ -80,7 +107,7 @@ bomly scan \ -o cyclonedx=sbom.cdx.json ``` -`-o` can be passed multiple times. At most one may omit `=` (that one goes to stdout). See [SBOM formats](SBOM.md) for the format comparison. +`-o` can be passed multiple times. At most one may omit `=` (that one goes to stdout). When every `-o` has a file path and no `--format` is set, a successful run writes the files and prints nothing — add `--format text` if you also want the terminal report. See [SBOM formats](SBOM.md) for the format comparison. ## Gate CI on a policy @@ -90,6 +117,16 @@ Add `--audit --fail-on ` to turn findings into a non-zero exit code: bomly scan --enrich --audit --fail-on high ``` +On a project with vulnerable packages, the report gains a Findings section and the process exits `2`: + +```text +Findings + [HIGH] GHSA-37ch-88jc-xwx2 path-to-regexp@0.1.7 + [HIGH] GHSA-9wv6-86v2-598j path-to-regexp@0.1.7 + [HIGH] GHSA-qwcr-r2fm-qrc7 body-parser@1.20.2 + [HIGH] GHSA-rhx6-c78j-4q9w path-to-regexp@0.1.7 +``` + Exit `0` means clean. Exit `2` means at least one finding matched the threshold. Exit `4` means an invalid flag value. See [Exit codes](EXIT_CODES.md). Common combinations: @@ -107,10 +144,26 @@ See [Auditors](AUDITORS.md) for the full grammar and [Reachability](REACHABILITY ## Explain why a package is in the graph ```bash -bomly explain lodash +bomly explain send ``` -Bomly prints the shortest dependency path that introduced the package, plus alternative paths if there are multiple roots. +Bomly prints every dependency path that introduces the package — not just the shortest one — so you can see each route you'd have to break to remove it: + +```text +ecosystem npm +manager npm +package send@0.18.0 +scope runtime +direct no +licenses + MIT [declared] +introduced by: + demo@1.0.0 + └─ express@4.19.2 + ├─ send@0.18.0 [analyzed] (transitive) + └─ serve-static@1.15.0 + └─ send@0.18.0 [analyzed] (transitive) +``` ## Diff two versions diff --git a/docs/INTEGRATIONS.md b/docs/INTEGRATIONS.md new file mode 100644 index 00000000..ec687013 --- /dev/null +++ b/docs/INTEGRATIONS.md @@ -0,0 +1,52 @@ +# Integrations + +Tools and surfaces that Bomly plugs into. Entries are tagged **Official** (built and maintained by the Bomly project) or **Community** (maintained by their own authors — direct support questions to them). To suggest an addition, open a pull request that adds an entry in the same format. + +## CI / CD + +### Bomly Guard (Official) + +The turnkey GitHub Action: runs `bomly diff` against a pull request's merge base and reports dependency changes, findings, and an updatable PR comment, with optional SARIF upload to code scanning. +→ [bomly-dev/bomly-guard](https://github.com/bomly-dev/bomly-guard) · [Guard guide](BOMLY_GUARD.md) + +### Direct CLI recipes (Official) + +Drop-in pipeline snippets for GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and CircleCI, plus a pre-commit hook for local enforcement. +→ [CI Integration](CI_INTEGRATION.md) + +## AI agents and editors + +### MCP server (Official) + +`bomly mcp serve` is built into the binary and works with any MCP client that supports stdio transport. Documented host setups: Claude Code, Cursor, VS Code, GitHub Copilot, and Codex. +→ [MCP Server](MCP.md) + +### Agent guidance snippet (Official) + +A ready-made instruction block for `CLAUDE.md` / `AGENTS.md` / `copilot-instructions.md` that has coding agents run a dependency diff before committing lockfile changes. +→ [MCP Server → Agent workflows](MCP.md) + +## GitHub code scanning + +SARIF 2.1.0 output uploads to the GitHub Security tab (and any other SARIF-aware tool) either via Guard's `upload-sarif` input or directly from the CLI. +→ [Output Formats → SARIF](OUTPUT_FORMATS.md#sarif--ci-security-tools) + +## Package managers and distribution + +Official install channels: Homebrew tap (`bomly-dev/tap`), WinGet (`Bomly.BomlyCLI`), Scoop, install scripts (`bomly.dev/install.sh`), Linux packages, `go install`, and prebuilt release archives with checksums and SLSA provenance. +→ [Installation](INSTALLATION.md) + +## Plugins + +External detectors, matchers, and auditors install as managed plugins (versioned, verified, disabled until enabled). Official plugin repositories: + +- **ClearlyDefined license matcher (Official)** — license enrichment from clearlydefined.io. → [bomly-plugin-clearlydefined-matcher](https://github.com/bomly-dev/bomly-plugin-clearlydefined-matcher) +- **EOL lifecycle matcher (Official)** — end-of-life status from endoflife.date. → [bomly-plugin-eol-matcher](https://github.com/bomly-dev/bomly-plugin-eol-matcher) +- **Bun lockfile detector (Official, example)** — reference implementation for plugin authors. → [bomly-plugin-bun-lock-detector](https://github.com/bomly-dev/bomly-plugin-bun-lock-detector) +- **Meme auditor (Official, example)** — a deliberately silly auditor showing the minimal auditor contract. → [bomly-plugin-meme-auditor](https://github.com/bomly-dev/bomly-plugin-meme-auditor) + +Write your own: [Plugins](PLUGINS.md) and the per-role implementation guides. + +## Community + +No community integrations are listed yet — if you've built one (a CI orb, an IDE extension, a dashboard that reads Bomly JSON), open a pull request adding it here with a one-line description and a link. diff --git a/docs/MATCHERS.md b/docs/MATCHERS.md index 6a96cdac..e9ec620b 100644 --- a/docs/MATCHERS.md +++ b/docs/MATCHERS.md @@ -32,7 +32,7 @@ Pass `--enrich` to run all default network matchers: bomly scan --enrich ``` -Use `--matchers` to restrict or extend the set with the standard `+/-` selector grammar: +Use `--matchers` to restrict or extend the set with the standard [selector grammar](COMMANDS.md#selector-grammar): ```bash # Only OSV diff --git a/docs/OUTPUT_FORMATS.md b/docs/OUTPUT_FORMATS.md index 177acded..b6d0dd83 100644 --- a/docs/OUTPUT_FORMATS.md +++ b/docs/OUTPUT_FORMATS.md @@ -40,6 +40,25 @@ The default. Groups packages by ecosystem and edge depth, summarizes finding cou bomly scan --enrich --audit ``` +```text +✓ 68 packages in 1 manifest (1 direct, 67 transitive · runtime 68, dev 0) + +✓ Enriched via Grype, deps.dev License Matcher + +✓ 7 fix suggestions for 7 of 7 vulnerable packages. + Run again with --format json to see remediation details. + +Top-level dependencies + NAME VERSION LICENSE SCOPE VULNS + express 4.19.2 MIT runtime 1L + +Findings + [HIGH] GHSA-37ch-88jc-xwx2 path-to-regexp@0.1.7 + [HIGH] GHSA-9wv6-86v2-598j path-to-regexp@0.1.7 + [HIGH] GHSA-qwcr-r2fm-qrc7 body-parser@1.20.2 + [HIGH] GHSA-rhx6-c78j-4q9w path-to-regexp@0.1.7 +``` + Markdown reports include the same remediation summary and the complete suggestion table. @@ -83,6 +102,21 @@ bomly explain lodash --json | jq '.paths[] | .nodes | map(.name) | join(" -> ")' bomly diff --base main --head HEAD --enrich --audit --json | jq '.findings.introduced[]' ``` +The first query against a project pinning `express@4.19.2` (first two of several matches shown): + +```json +{ + "name": "body-parser", + "version": "1.20.2", + "ecosystem": "npm" +} +{ + "name": "path-to-regexp", + "version": "0.1.7", + "ecosystem": "npm" +} +``` + JSON output includes Bomly-specific metadata that standard SBOM formats don't carry: reachability tier/status/confidence, audit reasons, and per-finding source. `bomly explain` returns every deterministic root-to-target path, not only a @@ -128,11 +162,41 @@ SARIF 2.1.0. Findings only. One result per (rule × package) pair. Includes: bomly scan --enrich --audit --fail-on high --format sarif > bomly.sarif ``` +
+Sample result object (one finding, properties trimmed) + +```json +{ + "ruleId": "GHSA-m6fv-jmcg-4jfg", + "level": "error", + "message": { + "text": "send vulnerable to template injection that can lead to XSS in pkg:npm/send@0.18.0" + }, + "locations": [ + { + "physicalLocation": { + "artifactLocation": { "uri": "package-lock.json" }, + "region": { "startLine": 636 } + } + } + ], + "properties": { + "package_ref": "pkg:npm/send@0.18.0", + "fixed_in": "0.19.0", + "fix_state": "fixed" + } +} +``` + +Locations point at the lockfile line that pins the vulnerable version, so code-scanning annotations land somewhere actionable. + +
+ GitHub Code Scanning, Azure DevOps, and most IDE extensions ingest SARIF directly. See [CI integration](CI_INTEGRATION.md) for upload recipes. ## Additional output: `-o` -`-o` uses the same format names as `--format`, plus an optional file path. Use `=` to write to a file, or just `` to write that additional output to stdout. +`-o` uses the same format names as `--format`, plus an optional file path. Use `=` to write to a file, or just `` to write that additional output to stdout. When every `-o` names a file and `--format` is not set, a successful run writes the files silently — pass `--format text` (or any primary format) if you also want stdout output. ```bash bomly scan --json \ diff --git a/docs/REACHABILITY.md b/docs/REACHABILITY.md index f7baaceb..f9189a5b 100644 --- a/docs/REACHABILITY.md +++ b/docs/REACHABILITY.md @@ -348,7 +348,7 @@ Reachability data appears in three places: ## Selecting analyzers -Use the `--analyzers` selector to restrict or extend the default set: +Use the `--analyzers` [selector](COMMANDS.md#selector-grammar) to restrict or extend the default set: ```sh bomly scan --enrich --analyze --analyzers govulncheck diff --git a/docs/README.md b/docs/README.md index fa2a4dc2..b04315d0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -49,6 +49,7 @@ Specifications and matrices. The generated pages are regenerated from code by `m Running Bomly in CI and keeping pipelines healthy. +- [Integrations](INTEGRATIONS.md) — CI actions, AI agents, code scanning, install channels, and plugins - [CI Integration](CI_INTEGRATION.md) — GitHub Actions, GitLab, Jenkins, Azure, CircleCI - [CI-Readiness Warnings](CI_READINESS.md) — package-manager, lockfile-format, and install-policy mismatches that fail CI on their own - [Bomly Guard](BOMLY_GUARD.md) — the turnkey GitHub Action for PR dependency review diff --git a/docs/SCAN_TARGETS.md b/docs/SCAN_TARGETS.md index 3600860b..f35b342d 100644 --- a/docs/SCAN_TARGETS.md +++ b/docs/SCAN_TARGETS.md @@ -39,6 +39,23 @@ bomly scan --recursive --exclude dist,examples # repeatable / comma-separated It works with `--path` and `--url` targets. `--image` and `--sbom` scans do not use directory discovery and reject `--recursive` with exit 4. +The report shows the discovered structure — every subproject with its manifest and package count, consolidated into one graph: + +```text +✓ 78 packages in 2 manifests (2 direct, 76 transitive · runtime 78, dev 0) + ├─ api (subproject, npm) + │ └─ demo — 68 packages [package-lock.json] + └─ web (subproject, npm) + └─ demo — 69 packages [package-lock.json] + +Top-level dependencies + NAME VERSION LICENSE SCOPE VULNS + express 4.19.2 MIT runtime - + express 4.21.2 MIT runtime - +``` + +Both versions of a package appear when different subprojects pin different releases — each is a distinct package keyed by its own PURL. + ### Depth — `--max-depth` Depth is counted from the scan root: the root itself is depth 0 and a direct child is depth 1. Directories at depths beyond `--max-depth` are not visited. The default is `3`; `--max-depth 0` removes the limit. `--max-depth` requires `--recursive`. @@ -175,6 +192,16 @@ SPDX 2.3 JSON and CycloneDX 1.6 JSON are auto-detected. Useful when: - A vendor sent you an SBOM and you want to evaluate it against your policy. - You're testing detector output without re-running the heavy detector. +Ingest looks like a normal scan, with one visible difference — SBOMs don't carry Bomly's runtime/development scope split, so dependencies keep the relationship the SBOM recorded (here, `required`) and count as `unscoped`: + +```text +✓ 69 packages in 1 manifest (1 direct, 68 transitive · runtime 0, dev 0, unscoped 69) + +Top-level dependencies + NAME VERSION LICENSE SCOPE VULNS + express 4.21.2 MIT required - +``` + See [SBOM formats](SBOM.md) for the format comparison. ## Combinations diff --git a/docs/USE_CASES.md b/docs/USE_CASES.md index ea8be634..1fe20f03 100644 --- a/docs/USE_CASES.md +++ b/docs/USE_CASES.md @@ -12,6 +12,37 @@ bomly diff --base main --head HEAD --enrich --audit --fail-on high `diff` classifies findings as introduced / resolved / persisted and only `--fail-on` matches against the introduced set, so a clean PR passes even on a repo with known debt. Exit code `2` means a new high finding; see [Exit codes](EXIT_CODES.md). +
+Sample output — an express upgrade that drags in one new advisory + +```text +Added (1) + + encodeurl@2.0.0 MIT runtime +Version changed (9) + ~ body-parser 1.20.2 → 1.20.3 + ~ cookie 0.6.0 → 0.7.1 + ~ express 4.19.2 → 4.21.2 + ~ finalhandler 1.2.0 → 1.3.1 + ~ merge-descriptors 1.0.1 → 1.0.3 + ~ path-to-regexp 0.1.7 → 0.1.12 + ~ qs 6.11.0 → 6.13.0 + ~ send 0.18.0 → 0.19.0 + ~ serve-static 1.15.0 → 1.16.2 + +1 new finding(s) introduced; 3 finding(s) persisted. + introduced [MEDIUM] GHSA-q8mj-m7cp-5q26 qs@6.13.0 + persisted [HIGH] GHSA-37ch-88jc-xwx2 path-to-regexp@0.1.12 + persisted [MEDIUM] GHSA-6rw7-vpxm-498p qs@6.13.0 + persisted [LOW] GHSA-w7fw-mjwx-w883 qs@6.13.0 + +✓ 2 fix suggestions for 2 of 2 vulnerable packages. + Run again with --format json to see remediation details. +``` + +With `--fail-on high`, this run passes: the only *introduced* finding is medium, and the persisted high is pre-existing debt. + +
+ → Turnkey version for GitHub PRs: the [Bomly Guard action](https://github.com/bomly-dev/bomly-guard) ([setup](CI_INTEGRATION.md#turnkey-pr-reviews-with-bomly-guard)). ## Generate and publish an SBOM @@ -125,10 +156,23 @@ You get added, removed, and updated dependencies, plus introduced/resolved findi **Goal:** find the path that pulled a transitive package into your build. ```bash -bomly explain lodash +bomly explain send +``` + +`explain` prints every dependency path that introduces the package: + +```text +package send@0.18.0 +direct no +introduced by: + demo@1.0.0 + └─ express@4.19.2 + ├─ send@0.18.0 [analyzed] (transitive) + └─ serve-static@1.15.0 + └─ send@0.18.0 [analyzed] (transitive) ``` -`explain` prints the dependency path(s) that introduced the package. Add `--audit` to see findings in that path's context. +Add `--audit` to see findings in that path's context. Full reference: [explain](commands/explain.md). ## Explore results interactively diff --git a/docs/manifest.json b/docs/manifest.json index 5939c0b1..00fb87d5 100644 --- a/docs/manifest.json +++ b/docs/manifest.json @@ -160,6 +160,12 @@ "description": "Every Bomly term, one sentence each.", "group": "reference" }, + { + "slug": "integrations", + "title": "Integrations", + "description": "CI actions, AI agents, code scanning, install channels, and plugins Bomly connects to.", + "group": "operations" + }, { "slug": "ci-integration", "title": "CI integration", diff --git a/internal/support/component_docs.go b/internal/support/component_docs.go index af38919c..bb7628c1 100644 --- a/internal/support/component_docs.go +++ b/internal/support/component_docs.go @@ -81,7 +81,7 @@ Bomly prefers native detectors because they preserve edges (needed by `+"`bomly ## Selecting detectors -Use `+"`--detectors`"+` to restrict or extend the default set with the standard `+"`+/-`"+` selector grammar: +Use `+"`--detectors`"+` to restrict or extend the default set with the standard [selector grammar](COMMANDS.md#selector-grammar): `+"```bash"+` # Use only the native Go detector @@ -266,7 +266,7 @@ Pass `+"`--enrich`"+` to run all default network matchers: bomly scan --enrich `+"```"+` -Use `+"`--matchers`"+` to restrict or extend the set with the standard `+"`+/-`"+` selector grammar: +Use `+"`--matchers`"+` to restrict or extend the set with the standard [selector grammar](COMMANDS.md#selector-grammar): `+"```bash"+` # Only OSV @@ -366,7 +366,7 @@ network. | [`+"`license`"+`](auditors/license.md) | Package licenses vs. allow/deny SPDX policy | `+"`--allow-license`"+`, `+"`--deny-license`"+`, `+"`--license-exempt-package`"+` | | [`+"`package`"+`](auditors/package.md) | Denied packages, typosquatted names, and source changes | `+"`--deny-package`"+`, `+"`--deny-group`"+`, `+"`--protected-package`"+`, `+"`--typosquat-threshold`"+`, `+"`--typosquat-mode`"+`, `+"`--fail-on source-change`"+` | -Select a subset with the `+"`--auditors`"+` selector (e.g. `+"`--auditors license`"+`). See the [per-auditor reference](auditors/) for options, examples, and limitations. Auditors are also a plugin extension point — for a worked example of an external auditor, see the [Meme Dependency Auditor](https://github.com/bomly-dev/bomly-plugin-meme-auditor). +Select a subset with the `+"`--auditors`"+` [selector](COMMANDS.md#selector-grammar) (e.g. `+"`--auditors license`"+`). See the [per-auditor reference](auditors/) for options, examples, and limitations. Auditors are also a plugin extension point — for a worked example of an external auditor, see the [Meme Dependency Auditor](https://github.com/bomly-dev/bomly-plugin-meme-auditor). ## When auditors run