github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #6847] I'd like to request a new feature for a workflow that runs a security scan when there is a change to the build system. #50833

New Issue
Open
opened 2026-04-28 17:13:45 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-28 17:13:45 -05:00
Owner
Copy Link

Originally created by @rempel1234 on GitHub (Sep 17, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6847

How's it going? I'd like to request when the build-system i.e. the Dockerfile, go.mod, requirements.txt etc. are updated, a workflow is triggered that scans a slimmed down resulting docker image and reports security issues. The general idea can be found in https://github.com/rempel1234/ollama/blob/main/.github/workflows/owasp-scan.yaml https://github.com/rempel1234/ollama/blob/main/.github/workflows/qa-sec.yml
https://github.com/rempel1234/ollama/blob/main/.github/workflows/virustotal.yaml
Currently, they'd still need to be fine-tuned to make sure the report is formatted properly (removing any non-high or critical findings, or findings that are accepted risks), consolidated into one workflow, remove all failure states, possibly change the reporting mechanism to be an email to hello@ollama... and the commits redone to be fewer commits, and more meaningful messages...

Originally created by @rempel1234 on GitHub (Sep 17, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6847 How's it going? I'd like to request when the build-system i.e. the Dockerfile, go.mod, requirements.txt etc. are updated, a workflow is triggered that scans a slimmed down resulting docker image and reports security issues. The general idea can be found in https://github.com/rempel1234/ollama/blob/main/.github/workflows/owasp-scan.yaml https://github.com/rempel1234/ollama/blob/main/.github/workflows/qa-sec.yml https://github.com/rempel1234/ollama/blob/main/.github/workflows/virustotal.yaml Currently, they'd still need to be fine-tuned to make sure the report is formatted properly (removing any non-high or critical findings, or findings that are accepted risks), consolidated into one workflow, remove all failure states, possibly change the reporting mechanism to be an email to hello@ollama... and the commits redone to be fewer commits, and more meaningful messages...
GiteaMirror added the feature request label 2026-04-28 17:13:45 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#50833
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?