search

noaione / spotilava

An implementation of Native Spotify player for Lavalink/Lavaplayer with Webserver as is intermediary.
MIT License
6 stars 0 forks source link

[ext] Tidal #3

Closed noaione closed 2 years ago

noaione commented 2 years ago

Implement a custom extension for Tidal playback.

The API support playing back all the audio format/quality and included metadata are injected automatically.

Decryption are included if needed too.

API Routes:

gitguardian[bot] commented 2 years ago

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Details of the secret
| Secret | Commit | Filename | Detected At | | | ------------------------- | ---------------- | --------------- | -------------------- | -------------------- | | Generic High Entropy Secret | 8e4d39aba798f06584d10dabb85f949f05a03b7a | internals/tidal/tidal.py | 07:21 November 26th, 2021 | [View secret](https://github.com/noaione/spotilava/commit/8e4d39aba798f06584d10dabb85f949f05a03b7a#diff-fe85355e2c1e24c11f60b963bb7558a3ef97656a2ed3b6fc8e747048ba9f6559R55) | | Generic High Entropy Secret | fe8abc5239e0357d9d70922f29c70427c5a1faee | internals/tidal/tidal.py | 07:46 November 26th, 2021 | [View secret](https://github.com/noaione/spotilava/commit/fe8abc5239e0357d9d70922f29c70427c5a1faee#diff-fe85355e2c1e24c11f60b963bb7558a3ef97656a2ed3b6fc8e747048ba9f6559L55) |
🛠 How to resolve this 1. Understand the implications of revoking this secret by examining where it is used in your code. 2. Replace and store your secret safely. Learn [here](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/detectors/specifics/private_key_openssh#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 4. If possible, [rewrite your git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to remove all evidence of the secret leak. Please beware this is not a trivial operation. You might completely break other contributing developers’ workflow and you risk accidentally deleting work in progress.

:bulb: To avoid such incidents in the future, consider following these best practices for managing and storing secrets including API keys and other credentials.

You are seeing this because you or someone else has authorized GitGuardian to scan pull requests