@gebarbilling/js
Browser-safe GebarBilling checkout and portal SDK.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped billing SDK package; name reflects org identity, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): False positive; package is a scoped billing SDK, not related to jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): False positive; unrelated scoped billing SDK. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): False positive; unrelated scoped billing SDK. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive; unrelated scoped billing SDK. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): False positive; unrelated scoped billing SDK. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 2 / 0 | |
| 0.4.0 | 2 / 0 | |
| 0.3.0 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.0 | 2 / 0 |
v0.4.1
2 findingsPackage name '@gebarbilling/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage name '@gebarbilling/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsPackage name '@gebarbilling/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.