Hack The Hacker

#11 Feedback_Idea

Inspiration

In today's internet world all information is at our fingertip, plagiarism is easy to perform and now ChatGPT will probably fuel this up. Whether its laziness or lack of time due to deadline, plagiarism is not only morally wrong but it also comes with legal consequences. This makes it essential to have a robust system in place to make sure it doesn’t happen at any level. Hack The Hacker tries to address the same.

What it does

For hackathon plagiarism can check the following -

1. Text based plagiarism in submission form entered text
2. Source Code based plagiarism in submitted application source code(github/code hosting weblink)

Tools basically run through this for each submission & generate score out of 100 to understand the level of possible plagiarism. This can be utilized in two different ways depending upon easiness. 1] For every submit button click, if there is change in text or Source code then run the system to generate score & inform the hacker to improve the same(let's say 85%) for submission eligibility. These is time-consuming but more effective way.

2] Let hacker do the submission & accept the same. In backend run the system to generate plagiarism score to decide the eligibility. Also, Score can be used in Tie-breaker submission to decide the winner.

How we built it

There are different tools available that helps to get plagiarism score. A] Text based -

 1] Grammarly - https://www.grammarly.com/plagiarism-checker 

 2] UniCheck - https://unicheck.com/

 3] PlagScan - https://www.plagscan.com/en/ 

 4] QueText - https://www.quetext.com/

B] Souce Code based -

1] Black Duck - https://www.synopsys.com/software-integrity/security-testing/software-composition-analysis.html 

2] UniCheck - https://unicheck.com/

Challenges we ran into

Nothing is free, there is cost to use any tool to its full limit. This can be turned advantage to enable only for hackathon sponsors who are ready to shell out more :)

Accomplishments that we're proud of

Possibly avoiding legal consequences to Sponsor, DevPost for plagiarized submissions.

What we learned

We should have system in place for any consequence which might not be in our hand.

What's next for Hack The Hacker

DevPost's call.

Note - Video attachment is taken from internet to give understanding of core idea.

Thanks for the read!!!

Built With

• experience