Paul Nothaft
0205c7dcce
Repo transferred from the-luap/picpeak → PicPeak/picpeak. Docker images
publish to ghcr.io/picpeak/picpeak/{backend,frontend} (lowercase, per the
GHCR canonical form computed by docker-build.yml's `${GITHUB_REPOSITORY,,}`).
Sweep covers:
- docker-compose.production.yml + Dockerfiles → new image registry path
- README, CONTRIBUTING, SECURITY, SIMPLE_SETUP, scripts/picpeak-setup.sh
→ new GitHub URLs
- Update-check / release-notes services (updateCheckService,
environmentService, updateNotificationService, adminSystem,
UpdateNotification, githubReleaseUrl) → GitHub API + tag URLs use the
canonical PicPeak/picpeak path
- Issue templates + README-DOCKER + workflow README → updated package URLs
- One commit-context comment in migrations/090 + customerAccountsService
CHANGELOG.md is intentionally untouched (historical release entries are
immutable; GitHub auto-redirects the old URLs indefinitely).
CLAUDE.md keeps the bare `(the-luap)` reference — that's the maintainer's
personal handle, not a repo URL.
22 files, 48/48 line swaps (every change is a 1:1 URL replacement).
37 lines
976 B
Markdown
37 lines
976 B
Markdown
---
|
|
name: Security Vulnerability
|
|
about: Report security issues privately
|
|
title: '[SECURITY] '
|
|
labels: 'security'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
⚠️ **IMPORTANT: For serious security vulnerabilities, please DO NOT create a public issue.**
|
|
|
|
Instead, please use [GitHub Private Vulnerability Reporting](https://github.com/PicPeak/picpeak/security/advisories/new) or email **[email protected]** with the details.
|
|
|
|
For minor security improvements or questions, you can use this template:
|
|
|
|
**Type of Security Issue**
|
|
- [ ] Authentication/Authorization
|
|
- [ ] Data Exposure
|
|
- [ ] Input Validation
|
|
- [ ] Configuration Issue
|
|
- [ ] Dependency Vulnerability
|
|
- [ ] Other: ___________
|
|
|
|
**Description**
|
|
Brief description of the security concern.
|
|
|
|
**Impact**
|
|
What could an attacker potentially do?
|
|
|
|
**Steps to Reproduce**
|
|
If applicable, how can this be reproduced?
|
|
|
|
**Suggested Fix**
|
|
If you have ideas on how to fix this issue.
|
|
|
|
**References**
|
|
Any relevant security advisories, CVEs, or documentation. |