Gathering detailed insights and metrics for cordova-background-geolocation-lt
Gathering detailed insights and metrics for cordova-background-geolocation-lt
Gathering detailed insights and metrics for cordova-background-geolocation-lt
Gathering detailed insights and metrics for cordova-background-geolocation-lt
react-native-background-geolocation
The most sophisticated cross-platform background location-tracking & geofencing module with battery-conscious motion-detection intelligence
@transistorsoft/capacitor-background-geolocation
The most sophisticated cross platform Capacitor background location tracking & geofencing module with battery-conscious motion-detection intelligence
cordova-background-geolocation-plugin
Cordova Background Geolocation Plugin
cordova-plugin-geolocation
Cordova Geolocation Plugin
npm install cordova-background-geolocation-lt
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
661 Stars
634 Commits
276 Forks
37 Watching
2 Branches
8 Contributors
Updated on 28 Nov 2024
Objective-C (50.98%)
JavaScript (21.15%)
Java (14.16%)
C++ (10.21%)
TypeScript (2.89%)
Shell (0.57%)
HTML (0.03%)
Cumulative downloads
Total Downloads
Last day
58.2%
242
Compared to previous day
Last week
19.4%
1,315
Compared to previous week
Last month
8.9%
5,307
Compared to previous month
Last year
17%
53,356
Compared to previous year
4
capacitor-background-geolocation
:stop_sign:The most sophisticated background location-tracking & geofencing module with battery-conscious motion-detection intelligence for iOS and Android.
The plugin's Philosophy of Operation is to use motion-detection APIs (using accelerometer, gyroscope and magnetometer) to detect when the device is moving and stationary.
When the device is detected to be moving, the plugin will automatically start recording a location according to the configured distanceFilter
(meters).
When the device is detected be stationary, the plugin will automatically turn off location-services to conserve energy.
Also available for Capacitor, React Native, Flutter.
The Android plugin requires purchasing a license. However, it will work for DEBUG builds. It will not work with RELEASE builds without purchasing a license.
(2018) This plugin is supported full-time and field-tested daily since 2013.
:warning: After installing the plugin, you must Configure the Plugin for both iOS & Android.
:warning: Cocoapods >= 1.10.0
is required.
1$ pod --version 2// if < 1.10.0 3$ sudo gem install cocoapods
1$ cordova plugin add cordova-background-geolocation-lt
1$ ionic cordova plugin add cordova-background-geolocation-lt
1npm install cordova-background-geolocation-lt 2npx cap sync
:information_source: See Capacitor Setup
1 <plugin name="cordova-background-geolocation-lt" source="npm"> 2 3 </plugin>
$ cordova plugin add https://github.com/transistorsoft/cordova-background-geolocation-lt.git
config.xml
: Add the following namespace attribute to the top-level <widget>
element:1<widget 2 id="com.foo.bar" 3 version="1.0.0" 4 xmlns="http://www.w3.org/ns/widgets" 5+ xmlns:android="http://schemas.android.com/apk/res/android" 6 xmlns:cdv="http://cordova.apache.org/ns/1.0">
<platform name="android">
container, add the license
key using a <config-file />
element:1<platform name="android"> 2 <!-- Cordova Background Geolocation License --> 3 <config-file parent="/manifest/application" target="app/src/main/AndroidManifest.xml"> 4 <meta-data 5 android:name="com.transistorsoft.locationmanager.license" 6 android:value="YOUR_LICENSE_KEY_HERE" /> 7 </config-file> 8</platform>
If you've purchased a license for the Polygon Geofencing add-on, add the following license key to your AndroidManifest
(Polygon Geofencing is fully functional in DEBUG builds so you can try before you buy):
1<platform name="android"> 2 <!-- Cordova Background Geolocation License --> 3 <config-file parent="/manifest/application" target="app/src/main/AndroidManifest.xml"> 4 <meta-data 5 android:name="com.transistorsoft.locationmanager.polygon.license" 6 android:value="YOUR_POLYGON_LICENSE_KEY_HERE" /> 7 </config-file> 8</platform>
If you've purchased an HMS Background Geolocation License for installing the plugin on Huawei devices without Google Play Services installed, add your HMS Background Geolocation license key:
1<platform name="android"> 2 <!-- Cordova Background Geolocation License --> 3 <config-file parent="/manifest/application" target="app/src/main/AndroidManifest.xml"> 4 <meta-data 5 android:name="com.transistorsoft.locationmanager.license" 6 android:value="YOUR_LICENSE_KEY_HERE" /> 7 </config-file> 8 <!-- HMS Background Geolocation License --> 9 <config-file parent="/manifest/application" target="app/src/main/AndroidManifest.xml"> 10 <meta-data 11 android:name="com.transistorsoft.locationmanager.hms.license" 12 android:value="YOUR_HMS_LICENSE_KEY_HERE" /> 13 </config-file> 14</platform>
:warning: Huawei HMS support requires cordova-background-geolocation >= 3.11.0
.
AlarmManager
"Exact Alarms" (optional)The plugin uses AlarmManager
"exact alarms" for precise scheduling of events (eg: Config.stopTimeout
, Config.motionTriggerDelay
, Config.schedule
). Android 14 (SDK 34), has restricted usage of "AlarmManager
exact alarms". To continue using precise timing of events with Android 14, you can manually add this permission to your AndroidManifest
. Otherwise, the plugin will gracefully fall-back to "in-exact AlarmManager
scheduling". For more information about Android's AlarmManager
, see the Android API Docs.
:open_file_folder: In your config.xml
, add the following block within the <platform name="android">
block (exactly as-shown:
1 <platform name="android"> 2 <config-file parent="/manifest" target="app/src/main/AndroidManifest.xml"> 3 <uses-permission android:minSdkVersion="34" android:name="android.permission.USE_EXACT_ALARM" /> 4 </config-file> 5 </platform>
:warning: It has been announced that Google Play Store has plans to impose greater scrutiny over usage of this permission (which is why the plugin does not automatically add it).
cordova-android >= 9.0.0
)It's highly recommended to configure your app for Android X when using Cordova 10 / cordova-android >= 9.0.0
.
1<platform name="android"> 2 <preference name="AndroidXEnabled" value="true" /> 3 . 4 . 5 . 6</platform>
:warning: If you see the following error, you need to configure your app for Android X.
java.lang.RuntimeException: Unable to get provider com.transistorsoft.locationmanager.util.LogFileProvider: java.lang.ClassNotFoundException
:warning: On older version of Cordova, If you change your license key after building android, you might receive an error:
1BUILD FAILED in 1s 2 3-Element meta-data#com.transistorsoft.locationmanager.license at AndroidManifest.xml duplicated 4-with element declared at AndroidManifest.xml duplicated with element declared at AndroidManifest.xml
Simply remove and re-add the android platform:
$ cordova platform remove android
$ cordova platform add android
Quite often, other 3rd-party plugins will require the same dependencies used by background-geolocation, including:
play-services:location
com.android.support
librariesokhttp
(Android HTTP library)If your app requests different versions of these dependencies, it can cause a build-failure (See wiki Solving Build Failures). Background Geolocation exposes the following Android CLI configuration --variable
to help you align the required dependency versions with other plugins:
Cordova CLI --variable
are used as follows:
:exclamation: To apply changes to these --variable
, you must remove/re-add the cordova platform(s)
$ cordova plugin add cordova-background-geolocation-lt --variable FOO=value_foo --variable BAR=value_bar
// After adding --variable, remove and re-add the platform
$ cordova platform remove android
$ cordova platform add android
@variable GOOGLE_API_VERSION ["20.+"]
Sets the desired version of play-services-location
dependency. Many other plugins require play-services
dependencies, (eg: cordova-plugin-googlemaps
, phonegap-plugin-push
): If the version of play-services
and/or firebase
is not aligned to the same version for ALL plugins, your build will fail.
$ cordova plugin add cordova-background-geolocation-lt --variable GOOGLE_API_VERSION=20.0.0
@variable OKHTTP_VERSION ["3.12.+"]
Sets the desired version of okhttp
to import. The Android plugin uses okhttp for its HTTP service. Some other plugins can also import okhttp
(eg: cordova-plugin-advanced-http
). If both plugins don't align themselves to the same version, your Android build will fail.
$ cordova plugin add cordova-background-geolocation-lt --variable OKHTTP_VERSION=3.12.+
iOS requires a number of "Usage Strings" for location and motion-usage authorization. iOS will render these strings upon the dialog used to request permission from the user. Take care to write relevent descriptions of why your app requires these authorizations as they can affect whether Apple accepts your app or not.
Paste all the following elements into the <platform name="ios">
container:
1<platform name="ios"> 2 <!-- background-geolocation --> 3 <config-file parent="NSLocationAlwaysAndWhenInUseUsageDescription" target="*-Info.plist"> 4 <string>[CHANGEME] Background location tracking is required for our app so we can...</string> 5 </config-file> 6 <config-file parent="NSLocationAlwaysUsageDescription" target="*-Info.plist"> 7 <string>[CHANGEME pre-iOS11. No longer used with iOS 12] Background location tracking is required for our app so we can...</string> 8 </config-file> 9 <config-file parent="NSLocationWhenInUseUsageDescription" target="*-Info.plist"> 10 <string>[CHANGEME] Background location tracking is required for our app so we can...</string> 11 </config-file> 12 <config-file parent="NSMotionUsageDescription" target="*-Info.plist"> 13 <string>[CHANGEME] Device motion updates help determine when the device is stationary so the app can save power by turning off location-updates</string> 14 </config-file> 15 <!-- /background-geolocation --> 16</platform>
Apple now requires apps provide a Privacy Manifest for "sensitive" APIs which could be abused for "fingerprinting" a user for malicious marketing activity.
:warning: You MUST upgrade your cordova-ios
platform to >= 7.1.0
for iOS Privacy Manifest Support:
config.xml
<privacy-manifest>
four block within the NSPrivacyAccessedAPITypes
container:1 <platform name="ios"> 2 <privacy-manifest> 3 <key>NSPrivacyAccessedAPITypes</key> 4 <array> 5 <!-- [1] cordova-background-fetch: UserDefaults --> 6 <dict> 7 <key>NSPrivacyAccessedAPIType</key> 8 <string>NSPrivacyAccessedAPICategoryUserDefaults</string> 9 10 <key>NSPrivacyAccessedAPITypeReasons</key> 11 <array> 12 <string>CA92.1</string> 13 </array> 14 </dict> 15 16 <!-- [2] cordova-background-geolocation: UserDefaults --> 17 <dict> 18 <key>NSPrivacyAccessedAPIType</key> 19 <string>NSPrivacyAccessedAPICategoryUserDefaults</string> 20 21 <key>NSPrivacyAccessedAPITypeReasons</key> 22 <array> 23 <string>CA92.1</string> 24 <string>1C8F.1</string> 25 </array> 26 </dict> 27 <!-- [3] cordova-background-geolocation (CocoaLumberjack): FileTimestamp --> 28 <dict> 29 <key>NSPrivacyAccessedAPIType</key> 30 <string>NSPrivacyAccessedAPICategoryFileTimestamp</string> 31 <key>NSPrivacyAccessedAPITypeReasons</key> 32 <array> 33 <string>C617.1</string> 34 <string>0A2A.1</string> 35 </array> 36 </dict> 37 <!-- [4] cordova-background-geolocation (CocoaLumberjack): DiskSpace --> 38 <dict> 39 <key>NSPrivacyAccessedAPIType</key> 40 <string>NSPrivacyAccessedAPICategoryDiskSpace</string> 41 <key>NSPrivacyAccessedAPITypeReasons</key> 42 <array> 43 <string>E174.1</string> 44 </array> 45 </dict> 46 </array> 47 </privacy-manifest> 48 </platform>
useSignificantChangesOnly
For those using useSignificantChangesOnly: true
, possibly because Apple denied your use of the background location
capability, you can disable background location
by providing the BACKGROUND_MODE_LOCATION
--variable
with an empty-string:
1$ cordova plugin add cordova-background-geolocation-lt --variable BACKGROUND_MODE_LOCATION="" 2 3$ cordova platform remove ios 4$ cordova platform add ios
There are three simple steps to using BackgroundGeolocation
:
#ready
the plugin.#start
the plugin.The plugin hosts its own Typescript API:
1// You may import any optional interfaces 2import BackgroundGeolocation, { 3 State, 4 Config, 5 Location, 6 LocationError, 7 Geofence, 8 HttpEvent, 9 MotionActivityEvent, 10 ProviderChangeEvent, 11 MotionChangeEvent, 12 GeofenceEvent, 13 GeofencesChangeEvent, 14 HeartbeatEvent, 15 ConnectivityChangeEvent 16} from "cordova-background-geolocation-lt"; 17 18class HomeView { 19 . 20 . 21 . 22 // Like any Cordova plugin, you must wait for Platform.ready() before referencing the plugin. 23 configureBackgroundGeolocation() { 24 // 1. Listen to events. 25 BackgroundGeolocation.onLocation(location => { 26 console.log('[location] - ', location); 27 }); 28 29 BackgroundGeolocation.onMotionChange(event => { 30 console.log('[motionchange] - ', event.isMoving, event.location); 31 }); 32 33 BackgroundGeolocation.onHttp(response => { 34 console.log('[http] - ', response.success, response.status, response.responseText); 35 }); 36 37 BackgroundGeolocation.onProviderChange(event => { 38 console.log('[providerchange] - ', event.enabled, event.status, event.gps); 39 }); 40 41 // 2. Configure the plugin with #ready 42 BackgroundGeolocation.ready({ 43 reset: true, 44 debug: true, 45 logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE, 46 desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH, 47 distanceFilter: 10, 48 url: 'http://my.server.com/locations', 49 autoSync: true, 50 stopOnTerminate: false, 51 startOnBoot: true 52 }, (state) => { 53 console.log('[ready] BackgroundGeolocation is ready to use'); 54 if (!state.enabled) { 55 // 3. Start tracking. 56 BackgroundGeolocation.start(); 57 } 58 }); 59 } 60}
1// Like any Cordova plugin, you must wait for deviceready before referencing the plugin. 2function onDeviceReady() { 3 // 1. Listen to events 4 var bgGeo = window.BackgroundGeolocation; 5 6 bgGeo.onLocation(function(location) { 7 console.log('[location] -', location); 8 }); 9 10 bgGeo.onMotionChange(function(event) { 11 console.log('[motionchange] -', event.isMoving, event.location); 12 }); 13 14 bgGeo.onHttp(function(response) { 15 console.log('[http] - ', response.success, response.status, response.responseText); 16 }); 17 18 bgGeo.onProviderChange(function(event) { 19 console.log('[providerchange] -', event.status, event.enabled, event.gps, event.network); 20 }); 21 22 // 2. Execute #ready method: 23 bgGeo.ready({ 24 reset: true, 25 debug: true, 26 logLevel: bgGeo.LOG_LEVEL_VERBOSE, 27 desiredAccuracy: bgGeo.DESIRED_ACCURACY_HIGH, 28 distanceFilter: 10, 29 url: 'http://my.server.com/locations', 30 autoSync: true, 31 stopOnTerminate: false, 32 startOnBoot: true 33 }, function(state) { // <-- Current state provided to #configure callback 34 // 3. Start tracking 35 console.log('BackgroundGeolocation is configured and ready to use'); 36 if (!state.enabled) { 37 bgGeo.start().then(function() { 38 console.log('- BackgroundGeolocation tracking started'); 39 }); 40 } 41 }); 42 43 // NOTE: Do NOT execute any API methods which will access location-services 44 // until the callback to #ready executes! 45 // 46 // For example, DO NOT do this here: 47 // 48 // bgGeo.getCurrentPosition(); // <-- NO! 49 // bgGeo.start(); // <-- NO! 50}
:information_source: NOTE: The configuration {}
provided to the #ready
method is applied only when your app is first booted — for every launch thereafter, the plugin will automatically load the last known configuration from persistant storage. If you wish to force the #ready
method to always apply the supplied config {}
, you can specify reset: true
1BackgroundGeolocation.ready({ 2 reset: true, // <-- true to always apply the supplied config 3 distanceFilter: 10 4}, function(state) { 5 console.log('- BackgroundGeolocation is ready: ', state); 6});
:warning: Do not execute any API method which will require accessing location-services until the callback to #ready
executes (eg: #getCurrentPosition
, #watchPosition
, #start
).
The BackgroundGeolocation
Javascript API supports Promises for nearly every method (the exceptions are #watchPosition
and adding event-listeners (eg: #onLocation
). For more information, see the API Documentation
1// Traditional API still works: 2BackgroundGeolocation.ready({desiredAccuracy: 0, distanceFilter: 50}).then(state => { 3 console.log('- BackgroundGeolocation is ready: ', state); 4}).catch(error => { 5 console.log('- BackgroundGeolocation error: ', error); 6});
A fully-featured SampleApp is available in its own public repo. After first cloning that repo, follow the installation instructions in the README there. This SampleApp includes a settings-screen allowing you to quickly experiment with all the different settings available for each platform.
If you're using XCode, boot the SampleApp in the iOS Simulator and enable Debug->Location->Freeway Drive
.
A simple Node-based web-application with SQLite database is available for field-testing and performance analysis. If you're familiar with Node, you can have this server up-and-running in about one minute.
cordova-background-geolocation
Copyright (c) 2018, Transistor Software (9224-2932 Quebec Inc)
All rights reserved.
sales@transistorsoft.com
http://transistorsoft.com
Preamble: This Agreement governs the relationship between YOU OR THE ORGANIZATION ON WHOSE BEHALF YOU ARE ENTERING INTO THIS AGREEMENT (hereinafter: Licensee) and Transistor Software, a LICENSOR AFFILIATION whose principal place of business is Montreal, Quebec, Canada (Hereinafter: Licensor). This Agreement sets the terms, rights, restrictions and obligations on using [{software}] (hereinafter: The Software) created and owned by Licensor, as detailed herein
License Grant: Licensor hereby grants Licensee a Personal, Non-assignable & non-transferable, Commercial, Royalty free, Including the rights to create but not distribute derivative works, Non-exclusive license, all with accordance with the terms set forth and other legal restrictions set forth in 3rd party software used while running Software.
2.1 Limited: Licensee may use Software for the purpose of: - Running Software on Licensee's Website[s] and Server[s]; - Allowing 3rd Parties to run Software on Licensee's Website[s] and Server[s]; - Publishing Software’s output to Licensee and 3rd Parties; - Distribute verbatim copies of Software's output (including compiled binaries); - Modify Software to suit Licensee’s needs and specifications.
2.2 Binary Restricted: Licensee may sublicense Software as a part of a larger work containing more than Software, distributed solely in Object or Binary form under a personal, non-sublicensable, limited license. Such redistribution shall be limited to unlimited codebases.
2.3 Non Assignable & Non-Transferable: Licensee may not assign or transfer his rights and duties under this license.
2.4 Commercial, Royalty Free: Licensee may use Software for any purpose, including paid-services, without any royalties
2.5 Including the Right to Create Derivative Works: Licensee may create derivative works based on Software, including amending Software’s source code, modifying it, integrating it into a larger work or removing portions of Software, as long as no distribution of the derivative works is made.
Term & Termination: The Term of this license shall be until terminated. Licensor may terminate this Agreement, including Licensee's license in the case where Licensee :
3.1 became insolvent or otherwise entered into any liquidation process; or
3.2 exported The Software to any jurisdiction where licensor may not enforce his rights under this agreements in; or
3.3 Licensee was in breach of any of this license's terms and conditions and such breach was not cured, immediately upon notification; or
3.4 Licensee in breach of any of the terms of clause 2 to this license; or
3.5 Licensee otherwise entered into any arrangement which caused Licensor to be unable to enforce his rights under this License.
Payment: In consideration of the License granted under clause 2, Licensee shall pay Licensor a FEE, via Credit-Card, PayPal or any other mean which Licensor may deem adequate. Failure to perform payment shall construe as material breach of this Agreement.
Upgrades, Updates and Fixes: Licensor may provide Licensee, from time to time, with Upgrades, Updates or Fixes, as detailed herein and according to his sole discretion. Licensee hereby warrants to keep The Software up-to-date and install all relevant updates and fixes, and may, at his sole discretion, purchase upgrades, according to the rates set by Licensor. Licensor shall provide any update or Fix free of charge; however, nothing in this Agreement shall require Licensor to provide Updates or Fixes.
5.1 Upgrades: for the purpose of this license, an Upgrade shall be a material amendment in The Software, which contains new features and or major performance improvements and shall be marked as a new version number. For example, should Licensee purchase The Software under version 1.X.X, an upgrade shall commence under number 2.0.0.
5.2 Updates: for the purpose of this license, an update shall be a minor amendment in The Software, which may contain new features or minor improvements and shall be marked as a new sub-version number. For example, should Licensee purchase The Software under version 1.1.X, an upgrade shall commence under number 1.2.0.
5.3 Fix: for the purpose of this license, a fix shall be a minor amendment in The Software, intended to remove bugs or alter minor features which impair the The Software's functionality. A fix shall be marked as a new sub-sub-version number. For example, should Licensee purchase Software under version 1.1.1, an upgrade shall commence under number 1.1.2.
Support: Software is provided under an AS-IS basis and without any support, updates or maintenance. Nothing in this Agreement shall require Licensor to provide Licensee with support or fixes to any bug, failure, mis-performance or other defect in The Software.
6.1 Bug Notification: Licensee may provide Licensor of details regarding any bug, defect or failure in The Software promptly and with no delay from such event; Licensee shall comply with Licensor's request for information regarding bugs, defects or failures and furnish him with information, screenshots and try to reproduce such bugs, defects or failures.
6.2 Feature Request: Licensee may request additional features in Software, provided, however, that (i) Licensee shall waive any claim or right in such feature should feature be developed by Licensor; (ii) Licensee shall be prohibited from developing the feature, or disclose such feature request, or feature, to any 3rd party directly competing with Licensor or any 3rd party which may be, following the development of such feature, in direct competition with Licensor; (iii) Licensee warrants that feature does not infringe any 3rd party patent, trademark, trade-secret or any other intellectual property right; and (iv) Licensee developed, envisioned or created the feature solely by himself.
Liability: To the extent permitted under Law, The Software is provided under an AS-IS basis. Licensor shall never, and without any limit, be liable for any damage, cost, expense or any other payment incurred by Licensee as a result of Software’s actions, failure, bugs and/or any other interaction between The Software and Licensee’s end-equipment, computers, other software or any 3rd party, end-equipment, computer or services. Moreover, Licensor shall never be liable for any defect in source code written by Licensee when relying on The Software or using The Software’s source code.
Warranty:
8.1 Intellectual Property: Licensor hereby warrants that The Software does not violate or infringe any 3rd party claims in regards to intellectual property, patents and/or trademarks and that to the best of its knowledge no legal action has been taken against it for any infringement or violation of any 3rd party intellectual property rights.
8.2 No-Warranty: The Software is provided without any warranty; Licensor hereby disclaims any warranty that The Software shall be error free, without defects or code which may cause damage to Licensee’s computers or to Licensee, and that Software shall be functional. Licensee shall be solely liable to any damage, defect or loss incurred as a result of operating software and undertake the risks contained in running The Software on License’s Server[s] and Website[s].
8.3 Prior Inspection: Licensee hereby states that he inspected The Software thoroughly and found it satisfactory and adequate to his needs, that it does not interfere with his regular operation and that it does meet the standards and scope of his computer systems and architecture. Licensee found that The Software interacts with his development, website and server environment and that it does not infringe any of End User License Agreement of any software Licensee may use in performing his services. Licensee hereby waives any claims regarding The Software's incompatibility, performance, results and features, and warrants that he inspected the The Software.
No Refunds: Licensee warrants that he inspected The Software according to clause 7(c) and that it is adequate to his needs. Accordingly, as The Software is intangible goods, Licensee shall not be, ever, entitled to any refund, rebate, compensation or restitution for any reason whatsoever, even if The Software contains material flaws.
Indemnification: Licensee hereby warrants to hold Licensor harmless and indemnify Licensor for any lawsuit brought against it in regards to Licensee’s use of The Software in means that violate, breach or otherwise circumvent this license, Licensor's intellectual property rights or Licensor's title in The Software. Licensor shall promptly notify Licensee in case of such legal action and request Licensee's consent prior to any settlement in relation to such lawsuit or claim.
Governing Law, Jurisdiction: Licensee hereby agrees not to initiate class-action lawsuits against Licensor in relation to this license and to compensate Licensor for any legal fees, cost or attorney fees should any claim brought by Licensee against Licensor be denied, in part or in full.
No vulnerabilities found.
Reason
13 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
license file detected
Details
Reason
binaries present in source code
Details
Reason
Found 0/29 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More