I haven't looked through the GitHub API, but is there a way to pull the description? I see "abandoned" or something similar in there more frequently than anywhere else; a browser plugin could fetch that data and display the tag moderately accurately. Or color based on last activity, etc. and that way you don't have to add a field.
edit: on second / third thought, maybe that's a possible solution: show the last-updated date when multiple repos are listed. I know I'd find that useful. What defines an "update" is debatable... commits? Issues? Wiki? All of the above? Something else?
You can always cram more data into another field, but now you've lost easy access to valuable metadata--this would be a hack, rather than a solution. Proposing for users to use a hack rather than a clean, semantically different, UI element is not good on your part as a designer.
A "Status" field benefits users as repository pages can have a prominent notification of the current status. You can also use it as a flag for searches to avoid having to wade through various abandoned projects before finding one that is being maintained.
And for the GitHub developers, it will provide a valuable statistic. Now they can track the progress and usage of repositories without potentially using assumptions like "Hmm, this repo has not be committed to for X days--could be abandoned?" or having to parse through the description/readme for keywords like "abandoned" or "no longer maintained", etc.
So yes, I would say that this simple metadata field would significantly benefit the users and developers.
My opinion is that every extra field I add to a page means I've personally failed. It's so easy to correlate databases to HTML that people often go feature-crazy adding fields to solve their problems and you end up with a product like JIRA.
However, as a designer I'm directly opposed to this idea. Every field I add to a web application torments me. I think about it constantly and scheme for hours trying to come up with any alternative to adding another field. I've been known to dream about "simply adding another field" for weeks. I need to make sure that this field is really going to positively impact my users. That it's more important than any other field already on the page.
So, would this inactive/status flag provide a significant benefit over editing the name/description/readme? I guess that's the question I'd like you guys to think about.