ppiankov/MongoSpectre Check
Audit MongoDB collection and index usage against repository code
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Feb 28, 2026
- License
- MIT
Pinned Snippet
uses: ppiankov/mongospectre-action@fad5a234028967c408f5ae77aa807406aad2ad6e # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| uri | MongoDB connection string | yes | — |
| repo-path | Path to repository to scan | no | . |
| database | Target database name | no | "" |
| format | Output format: text, json, sarif, or spectrehub | no | text |
| fail-on-missing | Exit with error if missing collections found | no | false |
| baseline | Path to baseline file for diff comparison | no | "" |
| version | MongoSpectre version to use (e.g., 0.3.0). Defaults to latest. | no | latest |
| args | Additional arguments to pass to mongospectre check | no | "" |
| upload-sarif | Upload SARIF results to GitHub Security tab (requires format=sarif) | no | false |
Outputs
| name | description |
|---|---|
| exit-code | Exit code from mongospectre check |
| report-path | Path to the generated report file |