@freik/git
Git files with filtering helper
13
Versions
Unlicense
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
freik
Keywords
nodejsbunjs-utilsdenogit
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established maintainer with clean track record; lack of Sigstore attestation is a process gap, not a security risk for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in bun-minified bundle output; pattern is from bundled dependency internals, not authored malicious code. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @freik/git package is a git utility, not a typosquat of 'got'; name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): 2-edit distance to 'vite' is too loose; @freik/git is clearly a git helper under a legitimate org scope. | ai | |
| phantom-deps | phantom-dep:@freik/typechk | AI (phantom-deps): Same-org dependency used as a type-check utility; declared in dependencies and externalized in build scripts. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.10 | 1 / 7 | |
| 0.3.9 | 1 / 7 | |
| 0.3.7 | 1 / 6 | |
| 0.3.5 | 1 / 6 | |
| 0.3.4 | 1 / 6 | |
| 0.3.3 | 1 / 6 | |
| 0.3.2 | 1 / 6 | |
| 0.3.1 | 1 / 6 | |
| 0.2.1 | 1 / 6 | |
| 0.2.0 | 1 / 6 | |
| 0.1.8 | 1 / 6 | |
| 0.1.1 | 1 / 6 | |
| 0.1.0 | 1 / 6 |
v0.1.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.