tamada / pelicode

83%

main: 83%

LAST BUILD ON BRANCH feature/multiple-databases

branch: feature/multiple-databases

CHANGE BRANCH

x

Reset

Sync Branches

• feature/multiple-databases
• ci/linux-arm64
• dependabot/cargo/zip-9.0.5
• docs/before-release
• docs/citation-orcid
• docs/contributing
• docs/release-notes-v0.1.0
• docs/release-procedure
• docs/scale-measurements
• feature/crate-readmes
• feature/enrich-doc-comments
• feature/initial-implementation
• feature/monthly-snapshots
• feature/oci-fetch
• feature/rename-cli-crate
• feature/snapshot
• feature/snapshot-annotations
• feature/snapshot-settings-action
• feature/staged
• feature/top-other-registries
• feature/updates
• fix/maven-prerelease
• fix/maven-sha1-comment
• fix/publish-permissions
• main
• release/v0.1.0

Build # 39092414680

Build Type

Pull #29

github

Committed by tamada

Commit Message

Check code against several databases at once

Snapshots are split by ecosystem, so scan takes --db more than once, and
database in the settings file may be a list. The databases must share
their feature parameters, which scan checks; the checked code is
featurized at the fingerprint levels of all of them.

pelicode_detect::detect_all runs one detector per database, so that
common code is left out with the package counts of each database, and
ranks the candidates of all of them together before --max-candidates.
Commands that work on one database ask for --db when the settings file
lists several. oci:// references in the settings file are no longer
taken as paths relative to it.

Closes #24

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Pull Request Pull Request #29: Check code against several databases at once

Coverage Stats

163 of 176 new or added lines in 6 files covered. (92.61%)

4111 of 4953 relevant lines covered (83.0%)

1435.97 hits per line