Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Security Scan: stop flagging pinned hashes and test fixtures on release PRs

Open Beginner friendly
  • Is something wrong?
#2,225 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python, typescript
Domain
ci-cd, security

Research direction

Start by inspecting the Security Scan workflow and its detect-secrets configuration, especially .secrets.baseline and the excludes described in the issue. Review the listed pinned hashes, test files, fixtures, and provider file to confirm which findings are false positives. Update the baseline or excludes as appropriate, then verify that a release PR scan reports only real findings.

Written by the indexing model from the issue text.

Description

code quality security

On the 2.2.0 release PR (#2214), Security Scan (detect-secrets, run 37994261254) failed on findings that are not secrets:

  • the sha256 pins in surfsense_local/backend/modules/runtime_packs/office/pin.py and a keyword in office/detect.py;
  • surfsense_local/electron/src/main/sidecars/python.test.ts and supervisor.test.ts;
  • the base64 fixtures in surfsense_local/frontend/src/features/docx-snapshot/fixtures/;
  • surfsense_backend/app/utils/proxy/providers/nodemaven.py:16.

None match the hook's excludes (.*/tests/.*, test_.*\.py), and the scan covers every file a release changes since main.

Done when: these are audited into .secrets.baseline or the excludes cover *.test.ts and fixtures/, so a release PR's scan shows only real findings.

Dominant language
Python
Stars
16.3k
Forks
1.6k
Avg merge
9h 15m
Merged PRs (30d)
254

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MODSetter/SurfSense

All issues in MODSetter/SurfSense

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.