Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong deploy commands reported by the build as code check for pkg:maven/dev.sigstore/[email protected] #937

Open
tromai opened this issue Dec 5, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@tromai
Copy link
Member

tromai commented Dec 5, 2024

Reproducing the issue

macaron analyze -purl pkg:maven/dev.sigstore/[email protected]

The Build As Code check passed with the following two deploy commands:

  • ["mvn", "clean", "deploy", "--no-transfer-progress", "$@"]
  • ["mvn", "clean", "deploy", "--no-transfer-progress", "$@"]

Initial investigation

Looking through its source code - https://github.com/sigstore/sigstore-java/tree/v1.0.0 shows that it's a Gradle project.

The 2 deploys commands are extracted from https://github.com/sigstore/sigstore-java/blob/d2603344a9357cb73142cb65caf5f39ddb428395/.github/workflows/examples.yaml (as shown in the database).

At this line it ran a shell script, which contains that mvn command - here.

Macaron reports 2 build tools for this PURL: gradle and maven.

@tromai tromai added the bug Something isn't working label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants