npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

user-data-for-fraud-prevention

v1.11.4

Published

Detects Timezone, screen size, scaling factor, browser plugins, local device IPs etc;

Downloads

495

Readme

user-data-for-fraud-prevention

user-data-for-fraud-prevention logo

CircleCI Coverage Status NPM Version semantic-release Contributions welcome code style: prettier

All Contributors

Description

This is an npm library to detect some browser or device details of the user such as Timezone, screen sizes, browser configuration etc. Such details are often required to be sent by software providers to the tax authority in their country to prevent fraud.

Eg: The Tax Authority in the UK (HMRC) requires software providers using some of their APIs to provide consistent headers known as Fraud Prevention headers. This node module collects such information for you in the format required.

Each top level folder in src/js has its own README with more specific information around the use case. E.g. HMRC README

How to use

Usage instructions can be found here

How to test

Instructions for testing the changes can be found here

Contributing

We do not allow contributors to claim issues. If you find something interesting you can contribute to the repo, feel free to raise a PR. We do not require you to let us know in advance.

  1. Fork the repo
  2. Install dependencies locally by running yarn
  3. Make your changes
  4. Make sure it builds using yarn build
  5. Run the tests (you added tests, right?) with yarn test
  6. Test your changes in your consuming code or using our demo project: Run yarn link
  7. Ensure the code coverage is the same or higher than before your changes
  8. Ensure commit message is properly formatted: type(subject): input. Eg: chore(prettier): update prettier to 2.x
  9. Create a PR to the master branch
  10. Codeowners will automatically be requested to review, so no need to tag on your PR

Expected Project Structure

The structure shown here is how your code should be organised in the repository

implementation folder should be renamed according to the problem you are solving for eg. the code for HMRC in UK is in the folder named hmrc.

Project
└──src
     └──js
        └──common                // Common and non specific code shoud be put in this folder
        └──implementation       // Implementation specific code for solving problem should be in this folder

How contributors get added to the README

There are two ways to add yourself as a contributor to this repo:

  1. Call @all-contributors bot by adding this following comment in a PR: @all-contributors please add [username] for [contributions]. Please refer to the docs for more info.
  2. Use the all-contributors-cli by running npx all-contributors add [username] [contributions]. Please refer to the docs for more info.

All parameters are required. See the Emoji Key (Contribution Types Reference) for a list of valid contribution types.

License

License

Changelog

Please see our CHANGELOG

Other Languages

README in other languages:

  1. Simplified Chinese
  2. Traditional Chinese
  3. Spanish
  4. German
  5. Hindi

Contributors