Add Copyright property

[alexeyzimarev]

Description

Add Copyright to props. Fixes #2295

[cloudflare-workers-and-pages]

Deploying restsharp with    Cloudflare Pages

Latest commit:	a217cf9
Status:	✅  Deploy successful!
Preview URL:	https://e3a7c638.restsharp.pages.dev
Branch Preview URL:	https://copyright.restsharp.pages.dev

View logs

[github-actions]

Test Results

   15 files     15 suites   5m 12s ⏱️
  446 tests   445 ✅ 0 💤 1 ❌
1 236 runs  1 233 ✅ 0 💤 3 ❌

For more details on these failures, see this check.

Results for commit a217cf9.

[qodo-merge-for-open-source]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡	🎫 #2295 🟢 Add a Copyright setting in the Directory.Build.props file Include Copyright information in the NuGet feed to make it clearly visible ⚪ Ensure copyright information is included in the package since the Authors setting alone is insufficient Address the issue that the Apache license does not link to the project's Apache license with copyright information
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label