verimu 0.0.2 → 0.0.3

package/README.md

@@ -2,19 +2,28 @@
 
 The NPM package for `verimu`, a tool for producing CRA-compliant SBOMs via CI / CD pipelines.
 
-## Current and Planned Support
+## Documentation and Website
 
-- [x] GitHub Actions
-- [ ] GitLab CI
-- [ ] Bitbucket Pipelines
+[https://verimu.com](https://verimu.com)
 
+## Supported CI / CD Platforms
 
-## Currently Supported Package Managers
+The core scanning pipeline is CI-agnostic — it works in any environment with Node.js 20+.
+Example CI configs are provided in the `ci-examples/` directory.
 
-- [x] npm
-- [ ] pip
-- [ ] go
-- [ ] cargo
+- [x] GitHub Actions (`.github/workflows/test.yml`)
+- [x] GitLab CI (`ci-examples/gitlab-ci.yml`)
+- [x] Bitbucket Pipelines (`ci-examples/bitbucket-pipelines.yml`)
+
+## Supported Package Ecosystems
+
+- [x] npm (package-lock.json)
+- [x] NuGet (packages.lock.json)
+- [x] pip (requirements.txt, Pipfile.lock)
+- [x] Cargo (Cargo.lock)
+- [x] Maven (pom.xml + dependency-tree.txt or `mvn` on PATH)
+- [x] Go (go.sum)
+- [x] Ruby (Gemfile.lock)
 
 ## Development
 
@@ -22,4 +31,15 @@ To run the tests, use:
 
 ```bash
 npm test
-```
+```
+
+## Maven Scanner Notes
+
+The Maven scanner needs resolved dependencies. Since Maven has no lockfile, it uses two strategies:
+
+1. **Pre-generated dependency tree** (recommended for CI): Run `mvn dependency:list -DoutputFile=dependency-tree.txt -DappendOutput=true` before scanning.
+2. **Auto-detect**: If `mvn` is on `$PATH`, the scanner runs `mvn dependency:list` automatically.
+
+## Three CI / CD Pipelines as Self Check on the `verimu` package itself
+
+There is a `bitbucket-pipelines.yml` and `.gitlab-ci.yml` in the root of the project, as well as a `.github/workflows/test.yml` file, all of which would run `verimu` against itself in each of the 3 frameworks we support (GitHub Actions, GitLab CI, Bitbucket Pipelines). The tests should pass in all 3 environments, confirming that `verimu` can successfully scan its own dependencies and produce a report.