Skip to content

Security: arish-mhrjn/aimodelinspector

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.x.x
< 1.0

Reporting a Vulnerability

We take the security of our project seriously. If you believe you have found a security vulnerability, please report it to us following these guidelines:

How to Report

  1. DO NOT create a public GitHub issue for the vulnerability
  2. Open a ticket with the following information:
    • A description of the vulnerability
    • Steps to reproduce the issue
    • Potential impact of the vulnerability
    • Any possible solutions you've identified

What to Expect

After you submit a report:

  1. You'll receive an acknowledgment within 48 hours
  2. We will investigate and provide an initial assessment within 5 business days
  3. We'll keep you informed about our progress
  4. Once the issue is resolved, we may ask for your feedback

Timeline

  • Initial Response: 48 hours
  • Assessment: 5 business days
  • Regular Updates: Every 3-5 days
  • Resolution Goal: Within 30 days

Our Commitments

  1. We will investigate all legitimate reports
  2. We will fix confirmed vulnerabilities as quickly as possible
  3. We will credit reporters (unless they decline) in our security advisories
  4. We will not take legal action against researchers who follow these guidelines

Safe Harbor

We consider security research conducted under this policy to be:

  • Authorized in accordance with the Computer Fraud and Abuse Act (CFAA)
  • Exempt from DMCA restrictions
  • Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research

Out of Scope

The following activities are prohibited:

  • Testing of systems other than those explicitly mentioned
  • Physical attacks against our infrastructure
  • Social engineering attacks
  • Denial of service attacks
  • Automated vulnerability scanning

Security Updates

Security updates will be released through our normal release channels with appropriate documentation and changelog entries.

Code of Conduct

While conducting security research, please:

  • Only test against test accounts you own
  • Delete any sensitive data you may inadvertently access
  • Do not access, modify, or delete other users' data
  • Do not disrupt our services
  • Cease testing and notify us immediately if you encounter sensitive data

This security policy is subject to change without notice. Please check back regularly for updates.

There aren’t any published security advisories