681 packages matching “RGCUAR-RW”
homebridge-kidde-ring
v0.1.0 · 2 months ago
Homebridge plugin for Kidde Smart Smoke + CO Alarms with Ring compatibility (RGCUAR-RW, RGSAR-RW, RGCUDR-RW). Exposes smoke, carbon monoxide, and battery state to Apple HomeKit with real-time push updates.
No known vulnerabilities
rw
v1.3.3 · 9 years ago
Now stdin and stdout are files.
No known vulnerabilities
@redwoodjs/api-server
v8.9.0 · 11 months ago
Redwood's HTTP server for Serverless Functions
No known vulnerabilities
read-write-mutexify
v2.1.0 · 3 years ago
Like mutexify but with read/write locks
No known vulnerabilities
parse-listing
v1.1.3 · 10 years ago
Small library to parse file listings into JavaScript objects
No known vulnerabilities
@cedarjs/auth
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
rw-shad
v2.4.1 · 1 year ago
Add shadcn components to a RedwoodJS project
No known vulnerabilities
@pmndrs/msdfonts
v1.0.76 · 26 days ago
base64 msdf fonts distributed as npm package
No known vulnerabilities
@cedarjs/auth-clerk-api
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-clerk-setup
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-clerk-web
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-auth0-web
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@redwoodjs/auth
v8.9.0 · 11 months ago
## Contributing
No known vulnerabilities
@cedarjs/auth-auth0-api
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-auth0-setup
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-dbauth-web
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supabase-api
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-custom-setup
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-netlify-api
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supertokens-api
v7.0.0 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities