@types/git-url-parse
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/git-up | AI (dependencies): Official @types sibling package, standard DefinitelyTyped pattern. | ai | |
| phantom-deps | phantom-dep:@types/git-up | AI (phantom-deps): Type-only convention dependency, not directly imported by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate DefinitelyTyped stub; tiny payload and sparse metadata are expected for this package type. | ai | |
| phantom-deps | phantom-dep:git-url-parse | AI (phantom-deps): Stub types package; git-url-parse is the peer it stubs, not a direct import. | ai |
v16.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.