Skip to content

docs: add SECURITY.md #232

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

Merged
Ron (rjaegers) merged 3 commits into from
Dec 5, 2023
Merged

docs: add SECURITY.md #232

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a0f8bd4
docs: add SECURITY.md
rjaegers Dec 5, 2023
1874ed7
chore: fix linter findings
rjaegers Dec 5, 2023
55cdf3d
ci: fix more linter findings
rjaegers Dec 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Security Policy

## Supported Versions

The [latest](https://github.com/philips-software/amp-devcontainer/releases/latest) version of
amp-devcontainer is supported with security updates.
The amp-devcontainer image is scanned for security vulnerabilities and the results are published on the
[code scanning](https://github.com/philips-software/amp-devcontainer/security/code-scanning) page.

## Reporting a Vulnerability

Vulnerabilities can be reported using GitHub's [private vulnerability reporting](https://github.com/philips-software/amp-devcontainer/security/advisories/new).
A member of the amp-devcontainer team will triage the reported vulnerability within a maximum of two business days.
If the vulnerability is accepted a [security advisory](https://github.com/philips-software/amp-devcontainer/security) will be published
and all further communication will be done via that security advisory.
Whenever an upstream fix is available the vulnerable package will be updated and a new release will be published
no later than five business days after a fix for the vulnerability has become available.