{"action":"published","release":{"url":"https://api.github.com/repos/sensational/sassphp/releases/1308198","assets_url":"https://api.github.com/repos/sensational/sassphp/releases/1308198/assets","upload_url":"https://uploads.github.com/repos/sensational/sassphp/releases/1308198/assets{?name}","html_url":"https://github.com/sensational/sassphp/releases/tag/v0.2.1","id":1308198,"tag_name":"v0.2.1","target_commitish":"master","name":"sassphp-0.2.1","draft":false,"author":{"login":"pilif","id":4990,"avatar_url":"https://avatars.githubusercontent.com/u/4990?v=3","gravatar_id":"","url":"https://api.github.com/users/pilif","html_url":"https://github.com/pilif","followers_url":"https://api.github.com/users/pilif/followers","following_url":"https://api.github.com/users/pilif/following{/other_user}","gists_url":"https://api.github.com/users/pilif/gists{/gist_id}","starred_url":"https://api.github.com/users/pilif/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pilif/subscriptions","organizations_url":"https://api.github.com/users/pilif/orgs","repos_url":"https://api.github.com/users/pilif/repos","events_url":"https://api.github.com/users/pilif/events{/privacy}","received_events_url":"https://api.github.com/users/pilif/received_events","type":"User","site_admin":false},"prerelease":false,"created_at":"2015-05-18T14:18:40Z","published_at":"2015-05-18T14:21:33Z","assets":[],"tarball_url":"https://api.github.com/repos/sensational/sassphp/tarball/v0.2.1","zipball_url":"https://api.github.com/repos/sensational/sassphp/zipball/v0.2.1","body":"sassphp now tracks libsass v3.2.2. This is the first release that is somewhat recommended for public use. Compared to earlier commits that didn't have a named version assoicated with, this fixes two important\r\npotential security issues:\r\n\r\n* in previous states, it was possible to overflow an internal buffer  by telling sassphp to compile a non-existing file with a long name.\r\n    \r\n    Unless you have let sassphp compile user-supplied paths, this won't affect you.\r\n* due to libsass unexpectedly freeing a buffer passed to it, when compiling a SASS string using sassphp, a buffer was freed twice. This is a classic double-free issue for which currently no known exploit exists."}}