Checking for code plagiarism with JavaScript

I was wondering how I can detect code plagiarism with Java开发者_如何学JAVAscript. I want to test assignment submissions for homework I'm going to hand out.

I've looked at using MOSS, but—from what I've heard—it's pretty poor for anything other than C. Unfortunately, I can't test it yet because I don't have submissions.

How can I go about detecting code plagiarism with JavaScript?

They claim that MOSS works on Javascript. Why don't you just try it. Write a Javascript file, then modify it, like a cheater would modify somebody elses code and feed it to MOSS to see what it says?

I build Clone detection tools, that find similar blocks of code across files. See CloneDR overview and example reports. CloneDR works for a wide variety of languages, and uses the langauge structure to makethe clone detection efficient and effective.

As per yar's comment pasting chunks of javascript into Google will work pretty well - but is stopping them cheating realistic?

Could you split the task into two parts, the first part allowing them to 'cheat' if they want to but tell them that there will be a second part of the task in class. Then have the class do exactly the same task in supervised class time.

If everyone has 'cheated' first time that's one thing. But if anyone is unable to redo their homework in class then they a) cheated (which is bad enough) and b) learnt nothing (which is worse).

Using the internet to 'research' is always going to happen - but its the ones who forget their 'research' that are cheating both you and themselves.

I wouldn't go out of my way to try and run through a plagiarism checker.

Code is code and bad code is bad code. People who can't code (those who are more likely to copy/paste code**) generally don't have good code. Difficulties (and questionable approaches around them) will be easily detectable if you even take a few seconds to check the source. Something just won't match up and it should smack you in the face.

**I would argue that adapted code isn't plagiarized unless it violates the authors distribution intent (e.g. violates copyright or license) and would encourage the students to simply document which existing resources, if any, they used as a base and/or incorporated as well as to encourage them to understand and adapt the code to fit their needs (and to make it better, so much code out there is soup). I do this all the time for "real programming work". Of course, it's not my curriculum :-)