
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Ruby wrapper for the e-conomic SOAP API, that aims at making working with the API bearable.
E-conomic is a web-based accounting system. For their marketing speak, see http://www.e-conomic.co.uk/about/. More details about their API at http://www.e-conomic.com/developer.
economic = Economic::Session.new
# Connect using a Private app ID and an access ID provided by the "Grant Access"
# As described here: http://www.e-conomic.com/developer/tutorials
economic = Economic::Session.new
economic.connect_with_token 'the_private_app_id', 'the_access_id_you_got_from_the_grant'
# Find a debtor:
debtor = economic.debtors.find(:id => 101)
# Creating a debtor:
debtor = economic.debtors.build
debtor.number = economic.debtors.next_available_number
debtor.debtor_group_handle = { :number => 1 }
debtor.name = 'Bob'
debtor.vat_zone = 'HomeCountry' # HomeCountry, EU, Abroad
debtor.currency_handle = { :code => 'DKK' }
debtor.price_group_handle = { :number => 1 }
debtor.is_accessible = true
debtor.ci_number = '12345678'
debtor.term_of_payment_handle = { :id => 1 }
debtor.layout_handle = { :id => 16 }
debtor.save
# Create invoice for debtor:
current_invoice = economic.current_invoices.build
current_invoice.date = Time.now
current_invoice.due_date = Time.now + 15
current_invoice.exchange_rate = 100
current_invoice.is_vat_included = false
invoice_line = Economic::CurrentInvoiceLine.new
invoice_line.description = 'Line on invoice'
invoice_line.unit_handle = { :number => 1 }
invoice_line.product_handle = { :number => 101 }
invoice_line.quantity = 12
invoice_line.unit_net_price = 19.95
current_invoice.lines << invoice_line
current_invoice.save
# You can delete it by doing:
# current_invoice.destroy
invoice = current_invoice.book
# Create a debtor payment
cash_book = economic.cash_books.all.last # Or find it by its number
# The reason debtor payments are done this way is because we don't want to specify the voucher number. If we build the cash book entry ourselves,
# without specifying the voucher number, the API will complain. This way, E-Conomics will assign a voucher number for us.
cash_book_entry = cash_book.entries.create_debtor_payment(:debtor_handle => debtor.handle, :contra_account_handle => { :number => '1920' })
cash_book_entry.amount = -123.45
cash_book_entry.currency_handle = { "Code" => "DKK" }
cash_book_entry.debtor_invoice_number = invoice.number
cash_book_entry.text = "Payment, invoice #{ invoice.number }"
cash_book_entry.save
cash_book.book
# Find a product:
product = economic.products.find(1234)
# Creating a product:
product = economic.products.build
product.number = 'ESC2014-LED-DISPLAY'
product.product_group_handle = { :number => 1 }
product.name = '100 meter LED display'
product.sales_price = 999999
product.cost_price = 100000
product.recommended_price = 999999
product.is_accessible = true
product.volume = 1
product.save
You need a Developer account and setup an app in their web UI. E-conomic users can then grant that app access to their account.
Not even remotely... For now, limited to a small subset of all the available operations:
| Create | Read | Update | Delete
-------------------+--------+------+--------+-------
CashBook | X | X | X | X
CashBookEntry | X | X | X | X
Company | X | X | X | X
Creditor | X | X | X | X
CreditorEntry | X | X | |
CreditorContact | X | X | X | X
CreditorEntry | X | X | X | X
CurrentInvoice | X | X | X | X
CurrentInvoiceLine | X | X | X | X
Debtor | X | X | X | X
DebtorContact | X | X | X | X
DebtorEntry | X | X | X | X
Entry | X | X | X | X
Invoice | X | X | |
Order | | X | |
OrderLine | | X | X |
Product | X | X | X | X
Sponsored by Lokalebasen.dk
R-conomic is licensed under the MIT license. See LICENSE for details.
FAQs
Unknown package
We found that rconomic 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.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.