If you discover a security problem in this repository seed:

1. Do not open a public issue with exploit details.
2. If private vulnerability reporting is enabled on GitHub, use it.
3. If it is not enabled yet, contact the repository maintainer through the repository owner profile and avoid posting sensitive details publicly.
4. Include:
   • affected file paths
   • impact
   • reproduction steps
   • suggested remediation if known

This repository currently contains documentation and repository-preparation surfaces for Lime. It does not yet expose a deployed runtime.

Security issues are therefore most likely to involve:

1. secret leakage in repository files;
2. unsafe publication guidance;
3. misleading trust or support signals;
4. future code when implementation is added.

Please allow maintainers reasonable time to investigate and remediate before public disclosure.