Skip to content

Security: SHOGO391/lp-kit

SECURITY.md

Security policy

Security updates apply to the latest commit on the default branch. Use an up-to-date checkout and lockfile. This is a personal project; there is no guaranteed response time or support SLA.

Report a vulnerability privately

Use GitHub private vulnerability reporting. Include the affected commit, impact, and reproduction steps using synthetic data. Do not put credentials, personal data, business records, or unpatched vulnerability details into public issues or pull requests.

If you exposed a credential, revoke or rotate it at its provider first. Deleting a file from the current branch does not remove earlier commits, forks, caches, logs, or downloaded copies.

Contributions and data

Keep local environment files, account tokens, private keys, local agent permissions, real user/business data, and generated caches out of Git. Use fictitious examples in tests. Keep dependency lockfiles and security checks current. Third-party dependencies retain their own licenses.

There aren't any published security advisories