Package Instance

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "http://public2.vulnerablecode.io/api/packages/52580?format=api",
    "purl": "pkg:npm/grunt-gh-pages@1.0.0",
    "type": "npm",
    "namespace": "",
    "name": "grunt-gh-pages",
    "version": "1.0.0",
    "qualifiers": {},
    "subpath": "",
    "is_vulnerable": false,
    "next_non_vulnerable_version": null,
    "latest_non_vulnerable_version": null,
    "affected_by_vulnerabilities": [],
    "fixing_vulnerabilities": [
        {
            "url": "http://public2.vulnerablecode.io/api/vulnerabilities/38048?format=api",
            "vulnerability_id": "VCID-z3v2-mvd3-y3fw",
            "summary": "Authentication credentails logged in clear text\nA common setup to deploy to gh-pages on every commit via a CI system is to expose a github token to ENV and to use it directly in the auth part of the url. In module the auth portion of the url is outputted as part of the grunt tasks logging function. If this output is publicly available then the credentials should be considered compromised.",
            "references": [],
            "fixed_packages": [
                {
                    "url": "http://public2.vulnerablecode.io/api/packages/52580?format=api",
                    "purl": "pkg:npm/grunt-gh-pages@1.0.0",
                    "is_vulnerable": false,
                    "affected_by_vulnerabilities": [],
                    "resource_url": "http://public2.vulnerablecode.io/packages/pkg:npm/grunt-gh-pages@1.0.0"
                }
            ],
            "aliases": [
                "GMS-2016-15"
            ],
            "risk_score": null,
            "exploitability": null,
            "weighted_severity": null,
            "resource_url": "http://public2.vulnerablecode.io/vulnerabilities/VCID-z3v2-mvd3-y3fw"
        }
    ],
    "risk_score": null,
    "resource_url": "http://public2.vulnerablecode.io/packages/pkg:npm/grunt-gh-pages@1.0.0"
}