fix(security): analytics.flisk.si sends no Permissions-Policy header, unlike readme and tools
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start by locating where the Worker assembles its shared response headers (the CSP mentioned in the issue is added there), likely in the request handler or a headers helper, and add Permissions-Policy: camera=(), microphone=(), geolocation=() to that set. Check how 404/error responses are built so the same header applies to them. Add tests asserting the header on GET / and on a 404, then run the existing test suite to confirm nothing regressed; done means the curl -sI check shows the header on both responses.
Written by the indexing model from the issue text.
Description
Problem
https://analytics.flisk.si/ sends a Content-Security-Policy but no Permissions-Policy header. readme.flisk.si and tools.flisk.si send camera=(), microphone=(), geolocation=(). Without it, any script or frame that ever runs on the page may ask for those browser features.
Reproduce: curl -sI https://analytics.flisk.si/ | grep -i permissions-policy prints nothing.
Root Cause Analysis
The security header set the app adds on responses includes CSP but leaves out Permissions-Policy.
TDD Fix Plan
- RED: Add a test that GET / returns a
Permissions-Policyheader that disables camera, microphone and geolocation.
GREEN: Add the header to the shared response header set. - RED: Add a test that the header is also present on 404 responses.
GREEN: Apply the header set to error responses too.
REFACTOR: Share one header helper with the other flisk.si sites.
Acceptance Criteria
- Permissions-Policy is present on pages and 404 responses
- Camera, microphone and geolocation are disabled
- All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·