sporeproject / spore-frontend Goto Github PK

I was thinking it would be interesting with an interactive gallery on the new website made in Unity where you can browse all the live NFT's in a mushroomy cave or something; this obviously needs to be developed further. I can personally start the development in a new repo and others could join in if interested.

Let me know what you think!

Your discord url in readme is invalid.

I PASSED MY SPORES TO AVAX TO GET GROW
BUT I CANT SEE ALL THEY AND I DONT KNOW HOW TO GET BACK ON MY WALLET ALL THEY.
THANKS

npm install doesn't work because react-lottie requires react 16 tops, and the project is using react 17. Lottie is working on their version 3, but until then it doesn't seem possible to make it work other than the --force flag which is not ideal.

Host: https://spore.earth/

Weakness: Clickjacking

Severity: Medium

DESCRIPTION:

Clickjacking is a portmanteau of two words ‘click’ and ‘hijacking’. It refers to hijacking a user's click for malicious intent. In it, an attacker embeds the vulnerable site in an transparent iframe in the attacker's own website and overlays it with objects such as buttons using CSS skills. This tricks users to perform unintended actions on vulnerable websites, thinking they are doing those on the attacker's website. Clickjacking, also known as a "UI redress attack".

IMPACT:

Users are tricked into performing all sorts of unintended actions such as typing in the password, clicking on ‘Delete my account’ button, liking a post, deleting a post, commenting on a blog. In other words all the actions that a normal user can do on a legitimate website can be done using clickjacking.

STEPS TO REPRODUCE:

1. Copy and paste the below HTML code.

2. Edit the src attribute of the iframe tag. Change its url to your target site and save the file.

3. Launch the file in browser.

4. Observe that the website is getting embedded in an Iframe.

MITIGATION:

In order to fix the issue, we must know the underlying reason that is causing the issue. Clickjacking is caused due to allowing permission to a third party website to embed the vulnerable site using Iframe. Disallowing this can be done by setting HTTP headers that direct the browser to not allow the target website to be iframed. This can be done by configuring the server on the following two response headers: X-Frame-Options Content-Security-Policy. Implement any one of the below based on your business requirements:

1. Content-Security-Policy: frame-ancestors ‘none’ : Set this if you want to disallow every domain from embedding your site in an Iframe.
2. Content-Security-Policy: frame-ancestors ‘self’ : Set this if you want to disallow every domain from embedding your site in an Iframe and allow only your domain (i.e. the site itself) to embed itself in Iframe.
3. Content-Security-Policy: frame-ancestors uri : Set this if you want to allow a specific uri to embed your site in an Iframe and disallow all the others.
   

You lack both formatting tools and linting to keep consistency. Sometimes you use single quotes, sometimes double. Sometime you end lines with semi colon, sometimes you don't.

I would recommend adding prettier for formatting and eslint for linting the typescript. Is that something that would interest you? I could make that happen. But a fair warning - the PR would involve lots of code changes and I would recommend you to test all functionality afterwards.

If you are interested we also need to discuss the formatting rules.
For example:

{
  "tabWidth": 2,
  "printWidth": 80,
  "trailingComma": "none",
  "arrowParens": "avoid"
}