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.
.. image:: https://travis-ci.org/iconfinder/pyvat.png?branch=master :target: https://travis-ci.org/iconfinder/pyvat
With EU VAT handling rules becoming ever more ridiculous and complicated, businesses within the EU are faced with the complexity of having to validate VAT numbers. pyvat
was built for Iconfinder's marketplace <http://www.iconfinder.com/>
_ to handle just this problem.
Validation of VAT numbers is performed in two steps: firstly, the VAT number is checked against an expression for the given country if one such is available, after which it is checked against a registry if one such is available.
Calculation of VAT rates for sales is supported within the EU for items covered by the new EU directive for VAT on telecommunications, broadcasting and electronic services <http://ec.europa.eu/taxation_customs/taxation/vat/how_vat_works/telecom/index_en.htm>
_.
To install requests, do yourself a favor and don't use anything other than pip <http://www.pip-installer.org/>
_:
.. code-block:: bash
$ pip install pyvat
pyvat
exposes its functionality through three simple methods:
pyvat.check_vat_number(vat_number, country_code=None)
Test if a VAT number is valid.
If possible, the VAT number will be checked against available registries.
:Parameters:
* vat_number
-- VAT number to validate.
* country_code
-- Optional country code. Should be supplied if known, as there is no guarantee that naively entered VAT numbers contain the correct alpha-2 country code prefix for EU countries just as not all non-EU countries have a reliable country code prefix. Default None
prompting detection.
:Returns:
True
if the VAT number can be fully asserted as valid or False
if not, otherwise None
indicating that the VAT number may or may not be valid.
pyvat.is_vat_number_format_valid(vat_number, country_code=None)
Test if the format of a VAT number is valid.
:Parameters:
* vat_number
-- VAT number to validate.
* country_code
-- Optional country code. Should be supplied if known, as there is no guarantee that naively entered VAT numbers contain the correct alpha-2 country code prefix for EU countries just as not all non-EU countries have a reliable country code prefix. Default None
prompting detection.
:Returns:
True
if the VAT number can be fully asserted as valid or False
if not, otherwise None
indicating that the VAT number may or may not be valid.
pyvat.get_sale_vat_charge(date, item_type, buyer, seller)
Get the VAT charge for performing the sale of an item.
Currently only supports determination of the VAT charge for telecommunications, broadcasting and electronic services in the EU.
:Parameters:
* date
(datetime.date
) -- Sale date.
* item_type
(pyvat.ItemType
) -- Type of the item being sold.
* buyer
(pyvat.Party
) -- Buyer.
* seller
(pyvat.Party
) -- Seller.
:Returns: The VAT charge to be applied to the sale of an item.
For more detailed documentation, see the full pyvat documentation <http://pyvat.readthedocs.org/>
_.
FAQs
VAT validation for Python
We found that pyvat demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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.