
Research
/Security News
DuckDB npm Account Compromised in Continuing Supply Chain Attack
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
layers-capacitor-biometric-auth
Advanced tools
npm i capacitor-biometric-auth
yarn add capacitor-biometric-auth
import { Plugins } from "@capacitor/core";
const { BiometricAuth } = Plugins;
const available = await BiometricAuth.isAvailable()
if (available.has) {
const authResult = await BiometricAuth.verify({...})
if (authResult.verified) {
// success authentication
} else {
// fail authentication
}
} else {
// biometric not available
}
Open biometric popup
option | values | decription |
---|---|---|
reason | any string | Popup label |
const result = await BiometricAuth.verify({reason: "Message ..."})
result
{
verified: true // true if biometric auth was succes or false otherwise,
status: {} // an object with errors matching biometric auth fails (on if verified === false)
}
status
error | description |
---|---|
10 | The user failed to provide valid credentials |
11 | Authentication was cancelled by application |
12 | The context is invalid |
13 | Not interactive |
14 | Passcode is not set on the device |
15 | Authentication was cancelled by the system |
16 | The user did cancel |
17 | The user chose to use the fallback |
Checks if biometric is enabled
const result = await BiometricAuth.isAvailable()
result
{
has: true, // true if has biometric auth enabled, false otherwise
status: {...} // an object with errors
}
status
error | description |
---|---|
1 | Biometric not available |
2 | Authentication could not continue because the user has been locked out of biometric authentication, due to failing authentication too many times. |
3 | Authentication could not start because the user has not enrolled in biometric authentication. |
FAQs
Complete
We found that layers-capacitor-biometric-auth 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
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.