@freik/git
Git files with filtering helper
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 | 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 11 of 11)
| 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 |
v0.3.10
2 findingsPackage name '@freik/git' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
2 findingsPackage name '@freik/git' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
2 findingsPackage name '@freik/git' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
2 findingsPackage name '@freik/git' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: freik.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.