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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@microsoft/fraud-protection

v1.1.0

Published

Microsoft Fraud Protection React Library

Readme

@microsoft/fraud-protection

Version

Getting started

  1. Install library

    from npm

    npm install @microsoft/fraud-protection --save

    from yarn

    yarn add @microsoft/fraud-protection
  2. Link native code

    With autolinking (react-native 0.60+)

    cd ios && pod install

    Pre 0.60

    react-native link @microsoft/fraud-protection

Usage

  1. You can initiate the SDK by following so it can start to collect device attributes.

    import RNFraudProtection from '@microsoft/fraud-protection';
    
    RNFraudProtection.start($tenantId);

    In this code, tenantId is the globally unique identifier (GUID) or universally unique identifier (UUID) that is provided by Microsoft.

  2. Send collected device attributes to Microsoft by calling send(). You can call send() in anywhere before or on the page that has the operation that you need a risk assessment for. For a sign-in/sign-up scenario, you can call send() immediately after start() call.

    import RNFraudProtection from '@microsoft/fraud-protection';
    
    RNFraudProtection.send($pageId); // Or RNFraudProtection.send()

    In this code, pageId is optional and can be set in the following way, depending on the scenario:

    • SI – Sign In
    • SU – Sign Up
    • P – Purchase
    • tst – Test
  3. Call getSessionId() to obtain the SessionId value that is required when the risk assessment APIs are called.

    import RNFraudProtection from '@microsoft/fraud-protection';
    
    RNFraudProtection.getSessionId((sessionId) => {
        console.log(sessionId)
    });

Runtime permissions

The React Native SDK relies on the following native runtime permissions to collect various device data. The SDK doesn't ask for any runtime permissions. The app should obtain these runtime permissions from the user.

  • Android

    • android.permission.ACCESS_COARSE_LOCATION
    • android.permission.READ_PHONE_STATE
    • android.permission.BLUETOOTH_CONNECT
  • iOS

    • The iOS SDK uses CLLocationManager, and checks for CLAuthorizationStatus.authorizedAlways or CLAuthorizationStatus.authorizedWhenInUse before it requests location data. The app should obtain CLLocationManager.requestWhenInUseAuthorization Or CLLocationManager.requestAlwaysAuthorization permission from the user.
    • The iOS SDK uses AppTrackingTransparency and checks for ATTrackingManager.AuthorizationStatus.authorized before it collects AdvertisingId. The app should obtain ATTrackingManager.requestTrackingAuthorization permission from the user.

Support

To log a support ticket, go to https://dfp.microsoft.com. (Global admin permissions are required.)