github-url-from-git
Parse a github git url and return the github repo url
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from tjholowaychuk to bcoe occurred in 2014 and is a well-known legitimate maintainer transition. bcoe is a trusted npm ecosystem contributor. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bcoe was added as maintainer in 2014 as part of a known legitimate handoff. No risk generalizes to future versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 0 / 6 | |
| 1.4.0 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 3 / 0 | |
| 1.0.0 | 3 / 0 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2014-07-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.