Merge remote-tracking branch 'origin/main'

.github/FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: itsjustshubh # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

SECURITY.md

@@ -0,0 +1,20 @@
+# Security Policy for Project Loading Screen
+## Supported Versions
+
+Security is a key priority for "Project Loading Screen," and we are dedicated to ensuring that our project remains secure for all users. The following table shows which versions of "Project Loading Screen" are currently being supported with security updates:
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.1.0   | :white_check_mark: |
+
+## Reporting a Vulnerability
+We take the security of "Project Loading Screen" seriously. If you discover a security vulnerability within the project, we encourage you to report it to us as soon as possible. We will investigate all legitimate reports and work swiftly to resolve any verified issues.
+
+## How to Report a Vulnerability
+1. Contact: Please report any suspected security vulnerabilities in private to [Your Email Address or Security Contact Page]. If possible, we appreciate reports being encrypted using our public key (available upon request).
+2. Response Time: We aim to acknowledge receipt of your report within 48 hours. After acknowledgment, we will provide regular updates about our progress towards a fix and a full announcement.
+3. Disclosure Policy: Once the issue has been resolved, we will release a public security advisory alongside the fix.
+4. Acknowledgment: While we do not currently offer a monetary bounty for security reports, we are happy to provide public recognition for responsible disclosures, except in cases where the reporter wishes to remain anonymous.
+5. Responsible Disclosure: We request that you do not disclose the issue publicly until we have had an opportunity to address it. We also ask you to avoid exploiting the vulnerability beyond what is necessary for demonstration purposes.
+
+Your efforts in responsibly disclosing your findings are greatly appreciated, and we will endeavor to acknowledge your contribution.