0bit-gate

v0.1.4 suspicious
6.0
Medium Risk

Official Python SDK for the 0Gate ramp API. Stripe-style ergonomics — secret keys, sessions, signed webhooks.

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package presents a moderate risk due to its recent creation, lack of historical data, and unverified maintenance credentials.

  • New package with no historical data
  • Non-existent repository
  • Potentially new maintainer account
Per-check LLM notes
  • Obfuscation: No obfuscation patterns detected, indicating low risk.
  • Credentials: No credential harvesting patterns detected, indicating low risk.
  • Metadata: The package is new with no history, a non-existent repository, and a potentially new maintainer account.

🔬 Heuristic Checks

Outbound Network Calls score 1.5

Found 1 network call pattern(s)

  • self._session = session or requests.Session() def request( self, *, method:
Code Obfuscation

No obfuscation patterns detected

Shell / Subprocess Execution

No shell execution patterns detected

Credential Harvesting

No credential harvesting patterns detected

Typosquatting

No typosquatting candidates detected

Registered Email Domain

No author email provided

Suspicious Page Links

All external links appear legitimate

Git Repository History score 3.0

Repository not found (deleted or private)

  • Repository not found (deleted or private)
Maintainer History score 6.0

3 maintainer concern(s) found

  • Only one version has ever been released — brand new package
  • Package uploaded less than 24 hours ago (2026-06-04T16:17:57.000Z)
  • Author "0Bit / 0Bit" appears to have only 1 package on PyPI (new or inactive account)
Known CVE Vulnerabilities

No known vulnerabilities found in OSV database.

💡 AI App Starter Prompt

Use this prompt to build a project with 0bit-gate
Create a fully functional mini-application that integrates the 0bit-gate Python package to manage payments using the 0Gate ramp API. Your application should allow users to create payment sessions, retrieve session details, and handle signed webhooks for successful transactions. Here are the steps and features your app should include:

1. **User Authentication**: Implement a simple user authentication system where users can sign up and log in. This will help in tracking individual payment sessions and securing user data.
2. **Payment Session Creation**: Allow authenticated users to initiate a payment session. Users should be able to specify the amount they wish to pay and any additional metadata like a description of the payment purpose.
3. **Session Details Retrieval**: After a payment session is initiated, provide a feature for users to view the details of their payment session, including the status of the payment and any errors encountered.
4. **Signed Webhook Handling**: Integrate the ability to receive and validate signed webhooks from the 0Gate ramp API. When a payment is successfully processed, the application should update the session status accordingly and notify the user via email or in-app message.
5. **Transaction History**: Keep a record of all transactions for each user, allowing them to review their past payments and session statuses.
6. **Admin Dashboard**: Develop an admin dashboard that allows administrators to monitor all payment activities, manage user accounts, and troubleshoot issues related to payment sessions.

Utilize the '0bit-gate' package throughout the development process to ensure smooth integration with the 0Gate ramp API. Pay special attention to the secret keys management and session handling as described in the package documentation. Ensure that your application is secure, user-friendly, and efficient.