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.

Sign up for GitHub

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

Jump to bottom

Accept an artifact file as input #498

Open
behnazh-w opened this issue Oct 3, 2023 · 0 comments
Open

Accept an artifact file as input #498

behnazh-w opened this issue Oct 3, 2023 · 0 comments
Labels
cli related to the Command-line Interface
Milestone
Support artifact ...

Comments

@behnazh-w
Copy link
Member

behnazh-w commented Oct 3, 2023 •
edited
Loading

Currently, to analyze an artifact we accept a Package URL (PURL) or repository path as input. We also need to accept the artifact file itself as input if available.

In cases where multiple artifacts are produced by a single release (commit), it would make sense to accept multiple artifacts as input.

Note that artifacts should be supported with the current data model in mind.
@behnazh-w behnazh-w added the cli related to the Command-line Interface label Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cli related to the Command-line Interface
Projects
None yet
Milestone
Support artifact and provenance files...
Development

No branches or pull requests
1 participant
@behnazh-w