{"action":"created","issue":{"url":"https://api.github.com/repos/swagger-api/swagger-node/issues/230","labels_url":"https://api.github.com/repos/swagger-api/swagger-node/issues/230/labels{/name}","comments_url":"https://api.github.com/repos/swagger-api/swagger-node/issues/230/comments","events_url":"https://api.github.com/repos/swagger-api/swagger-node/issues/230/events","html_url":"https://github.com/swagger-api/swagger-node/issues/230","id":90790354,"number":230,"title":"swagger-node-express's github now 301 redirects to here (swagger-api/swagger-node).","user":{"login":"Riobe","id":1712237,"avatar_url":"https://avatars.githubusercontent.com/u/1712237?v=3","gravatar_id":"","url":"https://api.github.com/users/Riobe","html_url":"https://github.com/Riobe","followers_url":"https://api.github.com/users/Riobe/followers","following_url":"https://api.github.com/users/Riobe/following{/other_user}","gists_url":"https://api.github.com/users/Riobe/gists{/gist_id}","starred_url":"https://api.github.com/users/Riobe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Riobe/subscriptions","organizations_url":"https://api.github.com/users/Riobe/orgs","repos_url":"https://api.github.com/users/Riobe/repos","events_url":"https://api.github.com/users/Riobe/events{/privacy}","received_events_url":"https://api.github.com/users/Riobe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-24T22:09:22Z","updated_at":"2015-08-10T03:18:57Z","closed_at":null,"body":"I'd create this as an issue on that repo, but I can't get to it and they were both belonging to swagger-api, so hopefully this is the right place to post this issue. The git repository link on the npm page for [swagger-node-express](https://www.npmjs.com/package/swagger-node-express) does a 301 permanent redirect to this repository.\r\n\r\nWe are using swagger-node-express at work and seeing the repository disappear for it is disconcerting at best. Can we know what happened? Perhaps the repository can be put back? My understanding is that if the repository is now deprecated that [npm deprecate](https://docs.npmjs.com/cli/deprecate) is the right way to go about it."},"comment":{"url":"https://api.github.com/repos/swagger-api/swagger-node/issues/comments/129287344","html_url":"https://github.com/swagger-api/swagger-node/issues/230#issuecomment-129287344","issue_url":"https://api.github.com/repos/swagger-api/swagger-node/issues/230","id":129287344,"user":{"login":"Riobe","id":1712237,"avatar_url":"https://avatars.githubusercontent.com/u/1712237?v=3","gravatar_id":"","url":"https://api.github.com/users/Riobe","html_url":"https://github.com/Riobe","followers_url":"https://api.github.com/users/Riobe/followers","following_url":"https://api.github.com/users/Riobe/following{/other_user}","gists_url":"https://api.github.com/users/Riobe/gists{/gist_id}","starred_url":"https://api.github.com/users/Riobe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Riobe/subscriptions","organizations_url":"https://api.github.com/users/Riobe/orgs","repos_url":"https://api.github.com/users/Riobe/repos","events_url":"https://api.github.com/users/Riobe/events{/privacy}","received_events_url":"https://api.github.com/users/Riobe/received_events","type":"User","site_admin":false},"created_at":"2015-08-10T03:18:57Z","updated_at":"2015-08-10T03:18:57Z","body":"Can the original repository be put back? Maybe you didn't like it, but you had published an npm package using that repo and for it to disappear like that after people were relying on it is incredibly frustrating. I lost a lot of hours due to that.\r\n\r\nIf you don't want to support it anymore deprecate it or something, but simply removing the repository and now only having the code as a tag in a repository for another project is not the right way. We've now stopped using any swagger-api repositories at my job."}}