starred/InstagramUnfollowers

Fork 0

mirror of https://github.com/davidarroyo1234/InstagramUnfollowers.git synced 2026-04-26 05:15:52 +03:00

[GH-ISSUE #171] Safe to use? Maybe a workflow to generate the compressed code to index.html #282

New issue

Closed

opened 2026-03-07 20:16:00 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:16:00 +03:00

Owner

Originally created by @realdennis on GitHub (May 22, 2024).
Original GitHub issue: https://github.com/davidarroyo1234/InstagramUnfollowers/issues/171

What a nice tool, thanks for the dedication on this!

Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this line.

It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138).

Would you consider to generate as a .js file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in github page release?

Originally created by @realdennis on GitHub (May 22, 2024). Original GitHub issue: https://github.com/davidarroyo1234/InstagramUnfollowers/issues/171 What a nice tool, thanks for the dedication on this! Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this [line](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/public/index.html#L260). It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138). Would you consider to generate as a `.js` file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in [github page release](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/.github/workflows/build_and_deploy_pages.yaml#L46)?

kerem closed this issue

2026-03-07 20:16:00 +03:00

kerem commented

2026-03-07 20:16:01 +03:00

Author

Owner

@davidarroyo1234 commented on GitHub (May 24, 2024):

What a nice tool, thanks for the dedication on this!

Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this line.

It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138).

Would you consider to generate as a .js file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in github page release?

The action its already doing that. Its doing the npm script and updating the index.html. You can check it in the action page and file

@davidarroyo1234 commented on GitHub (May 24, 2024): > What a nice tool, thanks for the dedication on this! > > Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this [line](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/public/index.html#L260). > > It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138). > > Would you consider to generate as a `.js` file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in [github page release](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/.github/workflows/build_and_deploy_pages.yaml#L46)? The action its already doing that. Its doing the npm script and updating the index.html. You can check it in the action page and file

kerem commented

2026-03-07 20:16:02 +03:00

Author

Owner

@davidarroyo1234 commented on GitHub (May 24, 2024):

What a nice tool, thanks for the dedication on this!

Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this line.

It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138).

Would you consider to generate as a .js file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in github page release?

Anyways if you dont trust that code, you can compile yourself the code and the output will be equal to the index.html one.

@davidarroyo1234 commented on GitHub (May 24, 2024): > What a nice tool, thanks for the dedication on this! > > Correct me if I'm wrong, I am not fully sure if there's any attack or logger in this [line](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/public/index.html#L260). > > It seems be manually pasted by yourself (or contributor) in the same commit (eg. #138). > > Would you consider to generate as a `.js` file or somewhat plaintext to public folder in your build rule in every relase (thru github action), and like embeded using some template/request approach in [github page release](https://github.com/davidarroyo1234/InstagramUnfollowers/blob/master/.github/workflows/build_and_deploy_pages.yaml#L46)? Anyways if you dont trust that code, you can compile yourself the code and the output will be equal to the index.html one.

No labels

bug

documentation

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/InstagramUnfollowers#282

No description provided.

Rows
Columns