[GH-ISSUE #726] Unnecessary `user-read-birthdate` and `user-read-email` scopes? #432

New issue

Closed

opened 2026-03-02 23:47:27 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 23:47:27 +03:00

Owner

Originally created by @sandersantema on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/726

Describe the bug
The user-read-birthdate and user-read-email scopes are included in the authentication process.

There's no user impact, but they do give a bit of concern. You could think: why would spotify-player want my email and birthday? I don't necessarily think a project with 4.4k stars would do anything nefarious, but it did raise an eyebrow for me. It seems it would be better to remove these scopes if they are indeed unnecessary.

Expected behaviour
No unnecessary scopes.

Originally created by @sandersantema on GitHub (May 15, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/726 **Describe the bug** The `user-read-birthdate` and `user-read-email` scopes are included in the authentication process. There's no user impact, but they do give a bit of concern. You could think: why would spotify-player want my email and birthday? I don't necessarily think a project with 4.4k stars would do anything nefarious, but it did raise an eyebrow for me. It seems it would be better to remove these scopes if they are indeed unnecessary. **Expected behaviour** No unnecessary scopes.

kerem

2026-03-02 23:47:27 +03:00

closed this issue
added the
good first issue
label

kerem commented

2026-03-02 23:47:28 +03:00

Author

Owner

@gumaath commented on GitHub (May 17, 2025):

Agreed, i think the user-read-birthdate maybe has some impact on Spotify's API, like explicit songs or something.

@gumaath commented on GitHub (May 17, 2025): Agreed, i think the `user-read-birthdate` maybe has some impact on Spotify's API, like explicit songs or something.

kerem commented

2026-03-02 23:47:28 +03:00

Author

Owner

@aome510 commented on GitHub (Jun 22, 2025):

Feel free to put up a PR and change it yourself. You can also make the passed scopes configurable

@aome510 commented on GitHub (Jun 22, 2025): Feel free to put up a PR and change it yourself. You can also make the passed scopes configurable

kerem commented

2026-03-02 23:47:28 +03:00

Author

Owner

@krishna4040 commented on GitHub (Jun 28, 2025):

Are these scopes safe to remove? can i put a PR?

@krishna4040 commented on GitHub (Jun 28, 2025): Are these scopes safe to remove? can i put a PR?

kerem commented

2026-03-02 23:47:28 +03:00

Author

Owner

@alexjyong commented on GitHub (Jul 8, 2025):

@krishna4040 fork the repo, remove the scopes, build the project with cargo build --release after setting up rust/cargo on your machine if you haven't already and see what happens I guess.

@alexjyong commented on GitHub (Jul 8, 2025): @krishna4040 fork the repo, remove the scopes, build the project with `cargo build --release` after setting up rust/cargo on your machine if you haven't already and see what happens I guess.

kerem referenced this issue

2026-03-02 23:49:42 +03:00

[PR #432] [MERGED] add CLI search command #761

kerem referenced this issue

2026-03-14 15:28:17 +03:00

[PR #432] [MERGED] add CLI search command #1700