Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
fountain_partner_api_client
Advanced tools
FountainPartnerApiClient - the Ruby gem for the Fountain Partner Docs
No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
This SDK is automatically generated by the OpenAPI Generator project:
To build the Ruby code into a gem:
gem build fountain_partner_api_client.gemspec
Then either install the gem locally:
gem install ./fountain_partner_api_client-0.0.5.gem
(for development, run gem install --dev ./fountain_partner_api_client-0.0.5.gem
to install the development dependencies)
or publish the gem to a gem hosting service, e.g. RubyGems.
Finally add this to the Gemfile:
gem 'fountain_partner_api_client', '~> 0.0.5'
If the Ruby gem is hosted at a git repository: https://github.com/GIT_USER_ID/GIT_REPO_ID, then add the following in the Gemfile:
gem 'fountain_partner_api_client', :git => 'https://github.com/GIT_USER_ID/GIT_REPO_ID.git'
Include the Ruby code directly using -I
as follows:
ruby -Ilib script.rb
Please follow the installation procedure and then run the following code:
# Load the gem
require 'fountain_partner_api_client'
# Setup authorization
FountainPartnerApiClient.configure do |config|
# Configure API key authorization: ApiKeyAuth
config.api_key['ApiKeyAuth'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['ApiKeyAuth'] = 'Bearer'
end
api_instance = FountainPartnerApiClient::DefaultApi.new
applicant_id = 'applicant_id_example' # String |
id = 'id_example' # String |
opts = {
v1_partners_id_applicants_applicant_id_details_post_request: FountainPartnerApiClient::V1PartnersIdApplicantsApplicantIdDetailsPostRequest.new # V1PartnersIdApplicantsApplicantIdDetailsPostRequest |
}
begin
#Create Applicant Details
result = api_instance.v1_partners_id_applicants_applicant_id_details_post(applicant_id, id, opts)
p result
rescue FountainPartnerApiClient::ApiError => e
puts "Exception when calling DefaultApi->v1_partners_id_applicants_applicant_id_details_post: #{e}"
end
All URIs are relative to http://localhost:3009
Class | Method | HTTP request | Description |
---|---|---|---|
FountainPartnerApiClient::DefaultApi | v1_partners_id_applicants_applicant_id_details_post | POST /v1/partners/{id}/applicants/{applicant_id}/details | Create Applicant Details |
FountainPartnerApiClient::DefaultApi | v1_partners_id_applicants_applicant_id_put | PUT /v1/partners/{id}/applicants/{applicant_id} | Update Applicant |
FountainPartnerApiClient::DefaultApi | v1_partners_id_applicants_applicant_id_status_post | POST /v1/partners/{id}/applicants/{applicant_id}/status | Create Applicant Status |
FountainPartnerApiClient::DefaultApi | v1_partners_id_get | GET /v1/partners/{id} | Show Partner |
FountainPartnerApiClient::DefaultApi | v1_partners_id_put | PUT /v1/partners/{id} | Update Partner |
FAQs
Unknown package
We found that fountain_partner_api_client demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.