+7 -6

ACCOUNT_MIGRATION.md

reviewed

··· 5 5 6 6 Therefore, we do not recommend migrating your primary account yet. And we specifically recommend _against_ migrating your main account if you do not understand how PLC operations work. 7 7 8 8 - As well, the Bluesky PDS is not currently accepting incoming migrations (it will in the future). Therefore this is currently a one-way street. If you migrate off of `bsky.social`, _you will not be able to return_. However, you will be able to migrate between other PDSs. 8 8 + Also, the Bluesky PDS is not currently accepting incoming migrations (it will in the future). Therefore this is currently a one-way street. If you migrate off of `bsky.social`, _you will not be able to return_. However, you will be able to migrate between other PDSs. 9 9 10 10  11 11 ··· 20 20 21 21 In order to create an account, you first need to prove to the new PDS that you're in control of the DID that you're attempting to register as. 22 22 23 23 - To do so, you need a JWT signed with the signing key associated with your DID. You can obtain this through calling `com.atproto.server.getServiceAuth` from your old PDS. If you're old PDS is not willing to provide the authentication token, you will need to update your DID document to point to a signing key that you possess in order to mint an authentication token yourself. 23 23 + To do so, you need a JWT signed with the signing key associated with your DID. You can obtain this through calling `com.atproto.server.getServiceAuth` from your old PDS. If your old PDS is not willing to provide the authentication token, you will need to update your DID document to point to a signing key that you possess in order to mint an authentication token yourself. 24 24 25 25 With this JWT set as a Bearer token, you can then create an account on the new PDS by calling `com.atproto.server.createAccount`. You'll need to fulfill any challenges that the new PDS requires - such as an invite code. 26 26 27 27 - After creating an account, you'll have a signing key on the new PDS and an empty repository. You're account will be in a "deactivated" state such that it is not usable yet. 27 27 + After creating an account, you'll have a signing key on the new PDS and an empty repository. Your account will be in a "deactivated" state such that it is not usable yet. 28 28 29 29 ### Migrating data 30 30 31 31 Now that you have an account on the new PDS, you can start migrating data into it. After creating your account, you will have received an access token for the new PDS and it will be required for all incoming data. 32 32 33 33 - First, you can grab your entire repository in the from of a [CAR file](https://ipld.io/specs/transport/car/carv1/) by calling `com.atproto.sync.getRepo`. You can then upload those exact bytes to your new PDS through `com.atproto.repo.importRepo`. The new PDS will parse the CAR file, index all blocks and records, and sign a new commit for the repository. 33 33 + First, you can grab your entire repository in the form of a [CAR file](https://ipld.io/specs/transport/car/carv1/) by calling `com.atproto.sync.getRepo`. You can then upload those exact bytes to your new PDS through `com.atproto.repo.importRepo`. The new PDS will parse the CAR file, index all blocks and records, and sign a new commit for the repository. 34 34 35 35 Next, you'll need to upload all relevant blobs. These can be discovered by calling `com.atproto.sync.listBlobs` on your old PDS. For each blob, you'll need to download the contents through `com.atproto.sync.getBlob` and upload them to your new PDS through `com.atproto.repo.uploadBlob`. 36 36 ··· 69 69 70 70 The below Typescript code gives an example of how this account migration flow may function. Please note that it is for documentation purposes only and can not be run exactly as is as there is an out-of-band step where you need to get a confirmation token from your email. 71 71 72 72 - It does also not handle some of the more advanced steps such as verifying a full import, looking for missing blobs, adding your own recovery key, or validating the PLC operation itself. 72 72 + It also does not handle some of the more advanced steps such as verifying a full import, looking for missing blobs, adding your own recovery key, or validating the PLC operation itself. 73 73 74 74 ```ts 75 75 import AtpAgent from '@atproto/api' ··· 107 107 108 108 const serviceJwtRes = await oldAgent.com.atproto.server.getServiceAuth({ 109 109 aud: newServerDid, 110 110 + lxm: 'com.atproto.server.createAccount', 110 111 }) 111 112 const serviceJwt = serviceJwtRes.data.token 112 113 ··· 200 201 await oldAgent.com.atproto.server.deactivateAccount({}) 201 202 } 202 203 203 203 - ``` 204 204 + ```

+2 -1

Dockerfile

reviewed

··· 1 1 FROM node:20.11-alpine3.18 as build 2 2 3 3 - RUN npm install -g pnpm 3 3 + RUN corepack enable 4 4 5 5 # Move files into the image and install 6 6 WORKDIR /app 7 7 COPY ./service ./ 8 8 + RUN corepack prepare --activate 8 9 RUN pnpm install --production --frozen-lockfile > /dev/null 9 10 10 11 # Uses assets from build stage to reduce build size

+67 -22

README.md

reviewed

··· 1 1 # PDS 2 2 3 3 - Welcome to the repository for the official Bluesky PDS (Personal Data Server). This repository includes container images and documentation designed to assist technical people with self-hosting a Bluesky PDS. 3 3 + Welcome to the repository for the official Bluesky PDS (Personal Data Server). This repository includes container images and documentation designed to assist technical people with hosting a Bluesky PDS. 4 4 5 5 - Head over to the [AT Protocol PDS Admins Discord](https://discord.gg/UWS6FFdhMe) to get started! 5 5 + Head over to the [AT Protocol PDS Admins Discord](https://discord.gg/e7hpHxRfBP) to chat with other folks hosting instances and get important updates about the PDS distribution! 6 6 7 7 ## Table of Contents 8 8 ··· 15 15 * [What is AT Protocol?](#what-is-at-protocol) 16 16 * [Where is the code?](#where-is-the-code) 17 17 * [What is the current status of federation?](#what-is-the-current-status-of-federation) 18 18 - * [What should I know about running a PDS in the developer sandbox?](#what-should-i-know-about-running-a-pds-in-the-developer-sandbox) 19 18 - [Self-hosting PDS](#self-hosting-pds) 20 19 * [Preparation for self-hosting PDS](#preparation-for-self-hosting-pds) 21 20 * [Open your cloud firewall for HTTP and HTTPS](#open-your-cloud-firewall-for-http-and-https) ··· 26 25 * [Creating an account using pdsadmin](#creating-an-account-using-pdsadmin) 27 26 * [Creating an account using an invite code](#creating-an-account-using-an-invite-code) 28 27 * [Using the Bluesky app with your PDS](#using-the-bluesky-app-with-your-pds) 28 28 + * [Setting up SMTP](#setting-up-smtp) 29 29 * [Updating your PDS](#updating-your-pds) 30 30 31 31 <!-- tocstop --> ··· 46 46 47 47 ### Where is the code? 48 48 49 49 - * [TypeScript code](https://github.com/bluesky-social/atproto) 49 49 + * [TypeScript code](https://github.com/bluesky-social/atproto/tree/main/packages/pds) 50 50 * [Go code](https://github.com/bluesky-social/indigo) 51 51 52 52 ### What is the current status of federation? 53 53 54 54 - As of Feb, 2024, the AT Protocol data service (PDS) is now open to federation for self-hosters! 54 54 + As of Spring 2024, the AT Protocol network is open to federation! 55 55 56 56 ✅ Federated domain handles (e.g. `@nytimes.com`) 57 57 ··· 61 61 62 62 ✅ Federated app views (API service) 63 63 64 64 - ✅ Federated data for self-hosters (PDS hosting) 64 64 + ✅ Federated data (PDS hosting) 65 65 66 66 ✅ Federated moderation (labeling) 67 67 68 68 - 🚧 Federated data for large service providers (coming soon) 69 69 - 70 70 - ### What should I know about running a PDS in the developer sandbox? 71 71 - 72 72 - Developers may now run self-hosted PDS hosts on the production network! 73 73 - 74 74 - Though it is still recommended to run experiments in the developer sandbox network. 75 75 - 76 76 - Read the [SANDBOX.md](https://github.com/bluesky-social/pds/blob/main/SANDBOX.md) for an overview of the sandbox network. 77 77 - 78 68 ## Self-hosting PDS 79 69 80 70 Self-hosting a Bluesky PDS means running your own Personal Data Server that is capable of federating with the wider Bluesky social network. 81 71 82 82 - > [!IMPORTANT] 83 83 - > Initially to join the network you'll need to join the [AT Protocol PDS Admins Discord](https://discord.gg/UWS6FFdhMe) and register the hostname of your PDS. We recommend doing so before bringing your PDS online. In the future, this registration check will not be required. 84 84 - 85 72 ### Preparation for self-hosting PDS 86 73 87 74 Launch a server on any cloud provider, [Digital Ocean](https://digitalocean.com/) and [Vultr](https://vultr.com/) are two popular choices. ··· 165 152 166 153 ### Verifying that your PDS is online and accessible 167 154 168 168 - You can check if your server is online and healthy by requesting the healthcheck endpoint. 155 155 + > [!TIP] 156 156 + > The most common problems with getting PDS content consumed in the live network are when folks substitute the provided Caddy configuration for nginx, apache, or similar reverse proxies. Getting TLS certificates, WebSockets, and virtual server names all correct can be tricky. We are not currently providing tech support for other configurations. 169 157 170 170 - You can visit `https://example.com/xrpc/_health` in your browser. You should see a JSON response with a version. 158 158 + You can check if your server is online and healthy by requesting the healthcheck endpoint. 171 159 172 172 - For example: 160 160 + You can visit `https://example.com/xrpc/_health` in your browser. You should see a JSON response with a version, like: 173 161 174 162 ``` 175 163 {"version":"0.2.2-beta.2"} 176 164 ``` 165 165 + 166 166 + You'll also need to check that WebSockets are working, for the rest of the network to pick up content from your PDS. You can test by installing a tool like `wsdump` and running a command like: 167 167 + 168 168 + ```bash 169 169 + wsdump "wss://example.com/xrpc/com.atproto.sync.subscribeRepos?cursor=0" 170 170 + ``` 171 171 + 172 172 + Note that there will be no events output on the WebSocket until they are created in the PDS, so the above command may continue to run with no output if things are configured successfully. 177 173 178 174 ### Creating an account using pdsadmin 179 175 ··· 204 200 1. Enter the URL of your PDS (e.g. `https://example.com/`) 205 201 206 202 _Note: because the subdomain TLS certificate is created on-demand, it may take 10-30s for your handle to be accessible. If you aren't seeing your first post/profile, wait 30s and try to make another post._ 203 203 + 204 204 + ### Setting up SMTP 205 205 + 206 206 + To be able to verify users' email addresses and send other emails, you need to set up an SMTP server. 207 207 + 208 208 + One way to do this is to use an email service. [Resend](https://resend.com/) and [SendGrid](https://sendgrid.com/) are two popular choices. 209 209 + 210 210 + Create an account and API key on an email service, ensure your server allows access on the required ports, and set these variables in `/pds/pds.env` (example with Resend): 211 211 + 212 212 + ``` 213 213 + PDS_EMAIL_SMTP_URL=smtps://resend:<your api key here>@smtp.resend.com:465/ 214 214 + PDS_EMAIL_FROM_ADDRESS=admin@your.domain 215 215 + ``` 216 216 + 217 217 + If you prefer to use a standard SMTP server (a local one or from your email provider), put your account's username and password in the URL: 218 218 + 219 219 + ``` 220 220 + PDS_EMAIL_SMTP_URL=smtps://username:password@smtp.example.com/ 221 221 + ``` 222 222 + 223 223 + Alternatively, if you're running a local sendmail-compatible mail service like Postfix or Exim on the same host, you can configure the PDS to use the sendmail transport by using such URL: 224 224 + 225 225 + ``` 226 226 + PDS_EMAIL_SMTP_URL=smtp:///?sendmail=true 227 227 + ``` 228 228 + 229 229 + _Note: Your PDS will need to be restarted with those variables. This varies depending on your setup. If you followed this installation guide, run `systemctl restart pds`. You might need to restart the server or recreate the container, depending on what you are using._ 230 230 + 231 231 + ### Logging 232 232 + 233 233 + By default, logs from the PDS are printed to `stdout` and end up in Docker's log. You can browse them by running: 234 234 + 235 235 + ``` 236 236 + [sudo] docker logs pds 237 237 + ``` 238 238 + 239 239 + Note: these logs are not persisted, so they will be lost after server reboot. 240 240 + 241 241 + Alternatively, you can configure the logs to be printed to a file by setting `LOG_DESTINATION`: 242 242 + 243 243 + ``` 244 244 + LOG_DESTINATION=/pds/pds.log 245 245 + ``` 246 246 + 247 247 + You can also change the minimum level of logs to be printed (default: `info`): 248 248 + 249 249 + ``` 250 250 + LOG_LEVEL=debug 251 251 + ``` 207 252 208 253 ### Updating your PDS 209 254

-168

SANDBOX.md

reviewed

··· 1 1 - # Bluesky Developer Sandbox Guide 2 2 - 3 3 - Welcome to the atproto federation developer sandbox! 4 4 - 5 5 - This is a completely separate network from our production services that allows us to test out the federation architecture and wire protocol. 6 6 - 7 7 - The federation sandbox environment is an area set up for exploration and testing of the technical components of the AT Protocol distributed social network. It is intended for developers and self-hosters to test out data availability in a federated environment. 8 8 - 9 9 - To maintain a positive and productive developer experience, we've established this Code of Conduct that outlines our expectations and guidelines. This sandbox environment is initially meant to test the technical components of federation. 10 10 - 11 11 - Given that this is a testing environment, we will be defederating from any instances that do not abide by these guidelines, or that cause unnecessary trouble, and will not be providing specific justifications for these decisions. 12 12 - 13 13 - <!-- markdown-toc -i SANDBOX.md --> 14 14 - 15 15 - <!-- toc --> 16 16 - 17 17 - - [Guidelines that must be followed](#guidelines-that-must-be-followed) 18 18 - * [Post responsibly](#post-responsibly) 19 19 - * [Keep the emphasis on testing](#keep-the-emphasis-on-testing) 20 20 - * [Do limit account creation](#do-limit-account-creation) 21 21 - * [Don’t expect persistence or uptime](#dont-expect-persistence-or-uptime) 22 22 - * [Don't advertise your service as being "Bluesky"](#dont-advertise-your-service-as-being-bluesky) 23 23 - * [Do not mirror sandbox did:plcs to production](#do-not-mirror-sandbox-didplcs-to-production) 24 24 - * [Status and Wipes](#status-and-wipes) 25 25 - + [🐉 Beware of dragons!](#%F0%9F%90%89-beware-of-dragons) 26 26 - + [Routine wipes](#routine-wipes) 27 27 - - [Getting started](#getting-started) 28 28 - * [Auto-updates](#auto-updates) 29 29 - * [Odds & Ends & Warnings & Reminders](#odds--ends--warnings--reminders) 30 30 - - [Learn more about atproto federation](#learn-more-about-atproto-federation) 31 31 - * [Network Services](#network-services) 32 32 - + [PLC](#plc) 33 33 - + [BGS](#bgs) 34 34 - + [Bluesky App View](#bluesky-app-view) 35 35 - - [The PDS](#the-pds) 36 36 - 37 37 - <!-- tocstop --> 38 38 - 39 39 - # Guidelines that must be followed 40 40 - 41 41 - Using the sandbox environment means you agree to adhere to our Guidelines. Please read the following carefully: 42 42 - 43 43 - ## Post responsibly 44 44 - 45 45 - The sandbox environment is intended to test infrastructure, but user content may be created as part of this testing process. Content generation can be automated or manual. 46 46 - 47 47 - Do not post content that requires active moderation or violates the [Bluesky Community Guidelines](https://bsky.social/about/support/community-guidelines). 48 48 - 49 49 - ## Keep the emphasis on testing 50 50 - 51 51 - We’re striving to maintain a sandbox environment that fosters learning and technical growth. We will defederate with instances that recruit users without making it clear that this is a test environment. 52 52 - 53 53 - ## Do limit account creation 54 54 - 55 55 - We don't want any one server using a majority of the resources in the sandbox. To keep things balanced, to start, we’re only federating with Personal Data Servers (PDS) with up to 1000 accounts. However, we may change this if needed. 56 56 - 57 57 - ## Don’t expect persistence or uptime 58 58 - 59 59 - We will routinely be wiping the data on our infrastructure. This is intended to reset the network state and to test sync protocols. Accounts and content should not be mirrored or migrated between the sandbox and real-world environments. 60 60 - 61 61 - ## Don't advertise your service as being "Bluesky" 62 62 - 63 63 - This is a developer sandbox and is meant for technical users. Do not promote your service as being a way for non-technical users to use Bluesky. 64 64 - 65 65 - ## Do not mirror sandbox did:plcs to production 66 66 - 67 67 - 68 68 - ## Status and Wipes 69 69 - 70 70 - ### 🐉 Beware of dragons! 71 71 - 72 72 - This hasn’t been production tested yet. It seems to work pretty well, but who knows what’s lurking under the surface — that's what this sandbox is for! Have patience with us as we prep for federation. 73 73 - 74 74 - On that note, please give us feedback either in [Issues](https://github.com/bluesky-social/atproto/issues) (actual bugs) or [Discussions](https://github.com/bluesky-social/atproto/discussions) (higher-level questions/discussions) on the [atproto repo](https://github.com/bluesky-social/atproto). 75 75 - 76 76 - ### Routine wipes 77 77 - 78 78 - As part of the sandbox, we will be doing routine wipes of all network data. 79 79 - 80 80 - We expect to perform wipes on a weekly or bi-weekly basis, though we reserve the right to do a wipe at any point. 81 81 - 82 82 - When we wipe data, we will be wiping it on all services (BGS, App View, PLC). We will also mark any existing DIDs as “invalid” & will refuse to index those accounts in the next epoch of the network to discourage users from attempting to “rollover” their accounts across wipes. 83 83 - 84 84 - # Getting started 85 85 - 86 86 - For complete instructions on getting your PDS set up, check out the [README](./README.md). 87 87 - 88 88 - To access your account, you’ll log in with the client of your choice in the exact same way that you log into production Bluesky, for instance the [Bluesky web client](https://app.bsky-sandbox.dev/). When you do so, please provide the url of *your PDS* as the service that you wish to log in to. 89 89 - 90 90 - ## Auto-updates 91 91 - 92 92 - We’ve included Watchtower in the PDS distribution. Every day at midnight PST, this will check our GitHub container registry to see if there is a new version of the PDS container & update it on your service. 93 93 - 94 94 - This will allow us to rapidly iterate on protocol changes, as we’ll be able to push them out to the network on a daily basis. 95 95 - 96 96 - When we do routine network wipes, we will be pushing out a database migration to participating PDS that wipes content and accounts. 97 97 - 98 98 - You are within your rights to disable Watchtower auto-updates, but we strongly encourage their use and will not be providing support if you decide not to run the most up-to-date PDS distribution. 99 99 - 100 100 - ## Odds & Ends & Warnings & Reminders 101 101 - 102 102 - 🧪 Experiment & have fun! 103 103 - 104 104 - 🤖 Run [feed generators](https://github.com/bluesky-social/feed-generator). They should work the exact same way as production - be sure to adjust your env to listen to Sandbox BGS! 105 105 - 106 106 - 🌈 Feel free to run your own AppView or BGS - although it’s a bit more involved & we’ll be providing limited support for this. 107 107 - 108 108 - ✏️ Because the atproto network is a distributed system, your PDS can no longer definitively read-after-write. Updates are generally processed pretty quickly, however this discrepancy may show in certain circumstances, such as updating a profile or replying to a thread. We're working on utilities to make this easier to handle. 109 109 - 110 110 - ⏱️ As a specific case of the above, because we use on-demand TLS with Caddy, your profile may not load at first - please be patient & it should load within 5-10s after account creation. Again, we'll be working to smooth over this. 111 111 - 112 112 - 👤 Your PDS will provide your handle by default. Custom domain handles should work exactly the same in sandbox as they do on production Bluesky. Although you will not be able to re-use your handle from production Bluesky as you can only have one DID set per handle. 113 113 - 114 114 - ⚠️ If you follow the self-hosted PDS setup instructions, you’ll have private key material in your env file - be careful about sharing that! 115 115 - 116 116 - 📣 This is a sandbox version of a **public broadcast protocol** - please do not share sensitive information. 117 117 - 118 118 - 🤝 Help each other out! Respond to issues & discussions, chat in [Matrix](https://matrix.to/#/%23bluesky-dev:matrix.org) or the community-run [Discord](https://discord.gg/3srmDsHSZJ), etc. 119 119 - 120 120 - # Learn more about atproto federation 121 121 - 122 122 - Check out the [high-level view of federation](https://bsky.social/about/blog/5-5-2023-federation-architecture). 123 123 - 124 124 - Dive deeper with the [atproto docs](https://atproto.com/docs). 125 125 - 126 126 - ## Network Services 127 127 - 128 128 - We are running three services: PLC, BGS, Bluesky "App View" 129 129 - 130 130 - ### PLC 131 131 - 132 132 - **Hostname:** `plc.bsky-sandbox.dev` 133 133 - 134 134 - **Code:** https://github.com/bluesky-social/did-method-plc 135 135 - 136 136 - PLC is the default DID provider for the network. DIDs are the root of your identity in the network. Sandbox PLC functions exactly the same as production PLC, but it is run as a separate service with a separate dataset. The DID resolution client in the self-hosted PDS package is set up to talk the correct PLC service. 137 137 - 138 138 - ### BGS 139 139 - 140 140 - **Hostname:** `bgs.bsky-sandbox.dev` 141 141 - 142 142 - **Code:** https://github.com/bluesky-social/indigo/tree/main/bgs 143 143 - 144 144 - BGS (Big Graph Service) is the firehose for the entire network. It collates data from PDSs & rebroadcasts them out on one giant websocket. 145 145 - 146 146 - BGS has to find out about your server somehow, so when we do any sort of write, we ping BGS with `com.atproto.sync.requestCrawl` to notify it of new data. This is done automatically in the self-hosted PDS package. 147 147 - 148 148 - If you’re familiar with the Bluesky production firehose, you can subscribe to the BGS firehose in the exact same manner, the interface & data should be identical 149 149 - 150 150 - ### Bluesky App View 151 151 - 152 152 - **Hostname:** `api.bsky-sandbox.dev` 153 153 - 154 154 - **Code:** https://github.com/bluesky-social/atproto/tree/main/packages/bsky 155 155 - 156 156 - The Bluesky App View aggregates data from across the network to service the Bluesky microblogging application. It consumes the firehose from the BGS, processing it into serviceable views of the network such as feeds, post threads, and user profiles. It functions as a fairly traditional web service. 157 157 - 158 158 - When you request a Bluesky-related view from your PDS (`getProfile` for instance), your PDS will actually proxy the request up to App View. 159 159 - 160 160 - Feel free to experiment with running your own App View if you like! 161 161 - 162 162 - # The PDS 163 163 - 164 164 - The PDS (Personal Data Server) is where users host their social data such as posts, profiles, likes, and follows. The goal of the sandbox is to federate many PDS together, so we hope you’ll run your own. 165 165 - 166 166 - We’re not actually running a Bluesky PDS in sandbox. You might see Bluesky team members' accounts in the sandbox environment, but those are self-hosted too. 167 167 - 168 168 - The PDS that you’ll be running is much of the same code that is running on the Bluesky production PDS. Notably, all of the in-pds-appview code has been torn out. You can see the actual PDS code that you’re running on the [atproto/simplify-pds](https://github.com/bluesky-social/atproto/pull/1198) branch.

+1

installer.sh

reviewed

··· 333 333 PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX=$(eval "${GENERATE_K256_PRIVATE_KEY_CMD}") 334 334 PDS_DATA_DIRECTORY=${PDS_DATADIR} 335 335 PDS_BLOBSTORE_DISK_LOCATION=${PDS_DATADIR}/blocks 336 336 + PDS_BLOB_UPLOAD_LIMIT=52428800 336 337 PDS_DID_PLC_URL=${PDS_DID_PLC_URL} 337 338 PDS_BSKY_APP_VIEW_URL=${PDS_BSKY_APP_VIEW_URL} 338 339 PDS_BSKY_APP_VIEW_DID=${PDS_BSKY_APP_VIEW_DID}

+2 -2

pdsadmin/help.sh

reviewed

··· 25 25 Takedown an account specified by DID. 26 26 e.g. pdsadmin account takedown did:plc:xyz123abc456 27 27 untakedown <DID> 28 28 - Remove a takedown an account specified by DID. 28 28 + Remove a takedown from an account specified by DID. 29 29 e.g. pdsadmin account untakedown did:plc:xyz123abc456 30 30 - password-reset <DID> 30 30 + reset-password <DID> 31 31 Reset a password for an account specified by DID. 32 32 e.g. pdsadmin account reset-password did:plc:xyz123abc456 33 33

+1

service/package.json

reviewed

··· 3 3 "private": true, 4 4 "version": "0.0.0", 5 5 "description": "Service entrypoint for atproto personal data server", 6 6 + "packageManager": "pnpm@8.15.9", 6 7 "main": "index.js", 7 8 "license": "MIT", 8 9 "dependencies": {

+139 -113

service/pnpm-lock.yaml

reviewed

··· 21 21 undici: 6.20.1 22 22 dev: false 23 23 24 24 + /@atproto-labs/fetch-node@0.1.7: 25 25 + resolution: {integrity: sha512-vZ627PQqVGiBmPxulnviIGvvBPpTdzOcnfU1WcLeES3E0WjNxRGQqFaodBl5Zc4cj3QSPG/KC6wPcj/rjhbDrQ==} 26 26 + engines: {node: '>=18.7.0'} 27 27 + dependencies: 28 28 + '@atproto-labs/fetch': 0.2.1 29 29 + '@atproto-labs/pipe': 0.1.0 30 30 + ipaddr.js: 2.2.0 31 31 + psl: 1.9.0 32 32 + undici: 6.20.1 33 33 + dev: false 34 34 + 24 35 /@atproto-labs/fetch@0.1.2: 25 36 resolution: {integrity: sha512-7mQQIRtVenqtdBQKCqoLjyAhPS2aA56EGEjyz5zB3sramM3qkrvzyusr55GAzGDS0tvB6cy9cDEtSLmfK7LUnA==} 26 37 dependencies: ··· 29 40 zod: 3.23.8 30 41 dev: false 31 42 43 43 + /@atproto-labs/fetch@0.2.1: 44 44 + resolution: {integrity: sha512-V22/7C7r+FfIDZA/BVn5UeuK5JccDp7nOiRfp5JITpVw2OXQbVfd8kywN7voWvPXw4sjd4cHoIPgQa0wvQGenQ==} 45 45 + dependencies: 46 46 + '@atproto-labs/pipe': 0.1.0 47 47 + optionalDependencies: 48 48 + zod: 3.23.8 49 49 + dev: false 50 50 + 32 51 /@atproto-labs/pipe@0.1.0: 33 52 resolution: {integrity: sha512-ghOqHFyJlQVFPESzlVHjKroP0tPzbmG5Jms0dNI9yLDEfL8xp4OFPWLX4f6T8mRq69wWs4nIDM3sSsFbFqLa1w==} 34 53 dev: false 35 54 36 36 - /@atproto-labs/simple-store-memory@0.1.1: 37 37 - resolution: {integrity: sha512-PCRqhnZ8NBNBvLku53O56T0lsVOtclfIrQU/rwLCc4+p45/SBPrRYNBi6YFq5rxZbK6Njos9MCmILV/KLQxrWA==} 55 55 + /@atproto-labs/simple-store-memory@0.1.2: 56 56 + resolution: {integrity: sha512-q6wawjKKXuhUzr2MnkSlgr6zU6VimYkL8eNvLQvkroLnIDyMkoCKO4+EJ885ZD8lGwBo4pX9Lhrg9JJ+ncJI8g==} 38 57 dependencies: 39 39 - '@atproto-labs/simple-store': 0.1.1 58 58 + '@atproto-labs/simple-store': 0.1.2 40 59 lru-cache: 10.2.0 41 60 dev: false 42 61 43 43 - /@atproto-labs/simple-store@0.1.1: 44 44 - resolution: {integrity: sha512-WKILW2b3QbAYKh+w5U2x6p5FqqLl0nAeLwGeDY+KjX01K4Dq3vQTR9b/qNp0jZm48CabPQVrqCv0PPU9LgRRRg==} 62 62 + /@atproto-labs/simple-store@0.1.2: 63 63 + resolution: {integrity: sha512-9vTNvyPPBs44tKVFht16wGlilW8u4wpEtKwLkWbuNEh3h9TTQ8zjVhEoGZh/v73G4Otr9JUOSIq+/5+8OZD2mQ==} 45 64 dev: false 46 65 47 66 /@atproto-labs/xrpc-utils@0.0.1: 48 67 resolution: {integrity: sha512-nenHwG6shq9p0tXX4HwoU8eWG23hveB4Jw0Y3VuKqHPMcSt3FQytV4POGe40X3opNERrYd406rtAAzHbOzKvhw==} 49 68 dependencies: 50 50 - '@atproto/xrpc': 0.6.6 51 51 - '@atproto/xrpc-server': 0.7.5 69 69 + '@atproto/xrpc': 0.6.9 70 70 + '@atproto/xrpc-server': 0.7.11 52 71 transitivePeerDependencies: 53 72 - bufferutil 54 73 - supports-color 55 74 - utf-8-validate 56 75 dev: false 57 76 58 58 - /@atproto/api@0.13.26: 59 59 - resolution: {integrity: sha512-W3zsgCdEuyvP2Qj3Np858kwjv5/pAd/pX3Z5HtLKIYt8uQottAZkuH+2dV+WRovgxHekyCyFJK07NuD4TQ9WMQ==} 77 77 + /@atproto/api@0.13.35: 78 78 + resolution: {integrity: sha512-vsEfBj0C333TLjDppvTdTE0IdKlXuljKSveAeI4PPx/l6eUKNnDTsYxvILtXUVzwUlTDmSRqy5O4Ryh78n1b7g==} 60 79 dependencies: 61 61 - '@atproto/common-web': 0.3.2 62 62 - '@atproto/lexicon': 0.4.5 63 63 - '@atproto/syntax': 0.3.1 64 64 - '@atproto/xrpc': 0.6.6 80 80 + '@atproto/common-web': 0.4.0 81 81 + '@atproto/lexicon': 0.4.7 82 82 + '@atproto/syntax': 0.3.3 83 83 + '@atproto/xrpc': 0.6.9 65 84 await-lock: 2.2.2 66 85 multiformats: 9.9.0 67 86 tlds: 1.250.0 68 87 zod: 3.23.8 69 88 dev: false 70 89 71 71 - /@atproto/aws@0.2.11: 72 72 - resolution: {integrity: sha512-IEcs1i/x+CbVM1RFZGb77ayN56Pyx9qZUqYDL1mQ3ZzkEQYwfdbS3UdIkagdZ/k1u51dbotd7WuavuF0c/YVVQ==} 90 90 + /@atproto/aws@0.2.15: 91 91 + resolution: {integrity: sha512-4fR7wEnlGtkchfL7XdQ61yALNbIMpX1xL4H0XEq+o3LzM7/08lw2vhQCDFCqqjOJwWXxefQRsVXG5p7iyy3HPA==} 92 92 + engines: {node: '>=18.7.0'} 73 93 dependencies: 74 74 - '@atproto/common': 0.4.6 75 75 - '@atproto/crypto': 0.4.2 76 76 - '@atproto/repo': 0.6.1 94 94 + '@atproto/common': 0.4.8 95 95 + '@atproto/crypto': 0.4.4 96 96 + '@atproto/repo': 0.6.5 77 97 '@aws-sdk/client-cloudfront': 3.515.0 78 98 '@aws-sdk/client-kms': 3.515.0 79 99 '@aws-sdk/client-s3': 3.515.0 80 100 '@aws-sdk/lib-storage': 3.515.0(@aws-sdk/client-s3@3.515.0) 81 81 - '@noble/curves': 1.3.0 101 101 + '@noble/curves': 1.8.1 82 102 key-encoder: 2.0.3 83 103 multiformats: 9.9.0 84 104 uint8arrays: 3.0.0 ··· 86 106 - aws-crt 87 107 dev: false 88 108 89 89 - /@atproto/common-web@0.3.2: 90 90 - resolution: {integrity: sha512-Vx0JtL1/CssJbFAb0UOdvTrkbUautsDfHNOXNTcX2vyPIxH9xOameSqLLunM1hZnOQbJwyjmQCt6TV+bhnanDg==} 109 109 + /@atproto/common-web@0.4.0: 110 110 + resolution: {integrity: sha512-ZYL0P9myHybNgwh/hBY0HaBzqiLR1B5/ie5bJpLQAg0whRzNA28t8/nU2vh99tbsWcAF0LOD29M8++LyENJLNQ==} 91 111 dependencies: 92 112 graphemer: 1.4.0 93 113 multiformats: 9.9.0 ··· 104 124 zod: 3.23.8 105 125 dev: false 106 126 107 107 - /@atproto/common@0.4.6: 108 108 - resolution: {integrity: sha512-X33ZubLPrHLNur2Ln4tRP5TY0G0u/t9DyAeA5dgtTNGIXE3iJIlfiUSR0PW5s1iAvBbrrJK4BwaA2Pqsdl+RNw==} 127 127 + /@atproto/common@0.4.8: 128 128 + resolution: {integrity: sha512-/etCtnWQGLcfiGhIPwxAWrzgzoGB22nMWMeQcU6xZgRT4Cqrfg3A08jAMIHqve/AQpL+6D82lHYp36CG7a5G0w==} 129 129 + engines: {node: '>=18.7.0'} 109 130 dependencies: 110 110 - '@atproto/common-web': 0.3.2 131 131 + '@atproto/common-web': 0.4.0 111 132 '@ipld/dag-cbor': 7.0.3 112 133 cbor-x: 1.5.8 113 134 iso-datestring-validator: 2.2.2 ··· 133 154 uint8arrays: 3.0.0 134 155 dev: false 135 156 136 136 - /@atproto/identity@0.4.4: 137 137 - resolution: {integrity: sha512-JtFmrVm1bWJl5c4iM3ymnZo32PV7gbt1gxBtYkT+ek7AxTLTyWlVue6emiMyLrURvIScbNkKqOTWlVh+GI/s9Q==} 157 157 + /@atproto/crypto@0.4.4: 158 158 + resolution: {integrity: sha512-Yq9+crJ7WQl7sxStVpHgie5Z51R05etaK9DLWYG/7bR5T4bhdcIgF6IfklLShtZwLYdVVj+K15s0BqW9a8PSDA==} 159 159 + engines: {node: '>=18.7.0'} 138 160 dependencies: 139 139 - '@atproto/common-web': 0.3.2 140 140 - '@atproto/crypto': 0.4.2 161 161 + '@noble/curves': 1.8.1 162 162 + '@noble/hashes': 1.7.1 163 163 + uint8arrays: 3.0.0 141 164 dev: false 142 165 143 143 - /@atproto/jwk-jose@0.1.2: 144 144 - resolution: {integrity: sha512-lDwc/6lLn2aZ/JpyyggyjLFsJPMntrVzryyGUx5aNpuTS8SIuc4Ky0REhxqfLopQXJJZCuRRjagHG3uP05/moQ==} 166 166 + /@atproto/identity@0.4.6: 167 167 + resolution: {integrity: sha512-fJq/cIp9MOgHxZfxuyki6mobk0QxRnbts53DstRixlvb5mOoxwttb9Gp6A8u9q49zBsfOmXNTHmP97I9iMHmTQ==} 168 168 + engines: {node: '>=18.7.0'} 145 169 dependencies: 146 146 - '@atproto/jwk': 0.1.1 170 170 + '@atproto/common-web': 0.4.0 171 171 + '@atproto/crypto': 0.4.4 172 172 + dev: false 173 173 + 174 174 + /@atproto/jwk-jose@0.1.4: 175 175 + resolution: {integrity: sha512-JzLn1wUzuLfweznSECdTjSHTxQBEz7Q8oJ4XKjRNludqzyJW8etEH00l1WolLipFxoj1QCG9qy00JmlC59Y6Rw==} 176 176 + dependencies: 177 177 + '@atproto/jwk': 0.1.3 147 178 jose: 5.2.2 148 179 dev: false 149 180 150 150 - /@atproto/jwk@0.1.1: 151 151 - resolution: {integrity: sha512-6h/bj1APUk7QcV9t/oA6+9DB5NZx9SZru9x+/pV5oHFI9Xz4ZuM5+dq1PfsJV54pZyqdnZ6W6M717cxoC7q7og==} 181 181 + /@atproto/jwk@0.1.3: 182 182 + resolution: {integrity: sha512-5rBgA8Fk4fg6MfNyEQvUnwq1MRn5xZOXYj4oxLuZ549XeNp2Rm2v+psuEkICD+o6pfIoMX4Hw7UTlXDrpsKKlQ==} 152 183 dependencies: 153 184 multiformats: 9.9.0 154 185 zod: 3.23.8 155 186 dev: false 156 187 157 157 - /@atproto/lexicon@0.4.5: 158 158 - resolution: {integrity: sha512-fljWqMGKn+XWtTprBcS3F1hGBREnQYh6qYHv2sjENucc7REms1gtmZXSerB9N6pVeHVNOnXiILdukeAcic5OEw==} 188 188 + /@atproto/lexicon@0.4.7: 189 189 + resolution: {integrity: sha512-/x6h3tAiDNzSi4eXtC8ke65B7UzsagtlGRHmUD95698x5lBRpDnpizj0fZWTZVYed5qnOmz/ZEue+v3wDmO61g==} 159 190 dependencies: 160 160 - '@atproto/common-web': 0.3.2 161 161 - '@atproto/syntax': 0.3.1 191 191 + '@atproto/common-web': 0.4.0 192 192 + '@atproto/syntax': 0.3.3 162 193 iso-datestring-validator: 2.2.2 163 194 multiformats: 9.9.0 164 195 zod: 3.23.8 165 196 dev: false 166 197 167 167 - /@atproto/oauth-provider@0.2.11: 168 168 - resolution: {integrity: sha512-leo6sMk1KSaYyN37s+Mj3xA7HYe6yYuFvdGfnrjdkzbCOprNshTXK2DHQCAT71kj2nBf68tvjyMOVN4b9bsvNg==} 198 198 + /@atproto/oauth-provider@0.2.17: 199 199 + resolution: {integrity: sha512-fvEbONJfjDRqQoIkB76n1cLz7y6f99Fhgs8h2u1LNZak1p95JZs3Tc5HsDhmUHo2Yk9h22CIwMRRjHImU/m1Nw==} 200 200 + engines: {node: '>=18.7.0'} 169 201 dependencies: 170 170 - '@atproto-labs/fetch': 0.1.2 171 171 - '@atproto-labs/fetch-node': 0.1.4 202 202 + '@atproto-labs/fetch': 0.2.1 203 203 + '@atproto-labs/fetch-node': 0.1.7 172 204 '@atproto-labs/pipe': 0.1.0 173 173 - '@atproto-labs/simple-store': 0.1.1 174 174 - '@atproto-labs/simple-store-memory': 0.1.1 175 175 - '@atproto/common': 0.4.6 176 176 - '@atproto/jwk': 0.1.1 177 177 - '@atproto/jwk-jose': 0.1.2 178 178 - '@atproto/oauth-types': 0.2.1 205 205 + '@atproto-labs/simple-store': 0.1.2 206 206 + '@atproto-labs/simple-store-memory': 0.1.2 207 207 + '@atproto/common': 0.4.8 208 208 + '@atproto/jwk': 0.1.3 209 209 + '@atproto/jwk-jose': 0.1.4 210 210 + '@atproto/oauth-types': 0.2.3 179 211 '@hapi/accept': 6.0.3 180 212 '@hapi/bourne': 3.0.0 181 213 '@hapi/content': 6.0.0 ··· 190 222 - supports-color 191 223 dev: false 192 224 193 193 - /@atproto/oauth-types@0.2.1: 194 194 - resolution: {integrity: sha512-hDisUXzcq5KU1HMuCYZ8Kcz7BePl7V11bFjjgZvND3mdSphiyBpJ8MCNn3QzAa6cXpFo0w9PDcYMAlCCRZHdVw==} 225 225 + /@atproto/oauth-types@0.2.3: 226 226 + resolution: {integrity: sha512-M+0WW/alS2BfhKtwvdU3rSaLoycw6kTH1kGKeyDdmb/xN/8QjU7T6dkJe+wX4NC7F23xdKfti9DZhBpEtn+/kg==} 195 227 dependencies: 196 196 - '@atproto/jwk': 0.1.1 228 228 + '@atproto/jwk': 0.1.3 197 229 zod: 3.23.8 198 230 dev: false 199 231 ··· 203 235 dependencies: 204 236 '@atproto-labs/fetch-node': 0.1.4 205 237 '@atproto-labs/xrpc-utils': 0.0.1 206 206 - '@atproto/api': 0.13.26 207 207 - '@atproto/aws': 0.2.11 208 208 - '@atproto/common': 0.4.6 238 238 + '@atproto/api': 0.13.35 239 239 + '@atproto/aws': 0.2.15 240 240 + '@atproto/common': 0.4.8 209 241 '@atproto/crypto': 0.4.2 210 210 - '@atproto/identity': 0.4.4 211 211 - '@atproto/lexicon': 0.4.5 212 212 - '@atproto/oauth-provider': 0.2.11 213 213 - '@atproto/repo': 0.6.1 242 242 + '@atproto/identity': 0.4.6 243 243 + '@atproto/lexicon': 0.4.7 244 244 + '@atproto/oauth-provider': 0.2.17 245 245 + '@atproto/repo': 0.6.5 214 246 '@atproto/syntax': 0.3.1 215 215 - '@atproto/xrpc': 0.6.6 216 216 - '@atproto/xrpc-server': 0.7.5 247 247 + '@atproto/xrpc': 0.6.9 248 248 + '@atproto/xrpc-server': 0.7.11 217 249 '@did-plc/lib': 0.0.4 218 250 '@hapi/address': 5.1.1 219 251 better-sqlite3: 10.1.0 220 252 bytes: 3.1.2 221 253 compression: 1.7.4 222 254 cors: 2.8.5 223 223 - disposable-email-domains-js: 1.8.0 255 255 + disposable-email-domains-js: 1.5.0 224 256 express: 4.18.2 225 257 express-async-errors: 3.1.1(express@4.18.2) 226 258 file-type: 16.5.4 227 227 - glob: 10.3.10 259 259 + glob: 10.3.12 228 260 handlebars: 4.7.8 229 261 http-terminator: 3.2.0 230 262 ioredis: 5.3.2 ··· 250 282 - utf-8-validate 251 283 dev: false 252 284 253 253 - /@atproto/repo@0.6.1: 254 254 - resolution: {integrity: sha512-dohNGgyLU3U58Fk/r0Rrs54tsCHT3iywmhA36slcDVOqxgJEyc+f7+1846KGCJThxEdTq0T1iXshoG7OpqPpYw==} 285 285 + /@atproto/repo@0.6.5: 286 286 + resolution: {integrity: sha512-Sa95LaEMDtwL9M0kp3vuVQIcgEJI+6EssDLIiuPnJAi9SbEPESdUfEiIR5t2oFCkMwrS7OJQCLdCa7CMy+plUg==} 287 287 + engines: {node: '>=18.7.0'} 255 288 dependencies: 256 256 - '@atproto/common': 0.4.6 257 257 - '@atproto/common-web': 0.3.2 258 258 - '@atproto/crypto': 0.4.2 259 259 - '@atproto/lexicon': 0.4.5 289 289 + '@atproto/common': 0.4.8 290 290 + '@atproto/common-web': 0.4.0 291 291 + '@atproto/crypto': 0.4.4 292 292 + '@atproto/lexicon': 0.4.7 260 293 '@ipld/car': 3.2.4 261 294 '@ipld/dag-cbor': 7.0.3 262 295 multiformats: 9.9.0 ··· 268 301 resolution: {integrity: sha512-fzW0Mg1QUOVCWUD3RgEsDt6d1OZ6DdFmbKcDdbzUfh0t4rhtRAC05KbZYmxuMPWDAiJ4BbbQ5dkAc/mNypMXkw==} 269 302 dev: false 270 303 271 271 - /@atproto/xrpc-server@0.7.5: 272 272 - resolution: {integrity: sha512-Jo69+gULH9RrmCxuCYJJLKbOW3HBB2IypuzYzTOPzf5WPdRkjJ46gUVF6t4PupPTIO9kLzluK41YuUhtkMaIdg==} 304 304 + /@atproto/syntax@0.3.3: 305 305 + resolution: {integrity: sha512-F1LZweesNYdBbZBXVa72N/cSvchG8Q1tG4/209ZXbIuM3FwQtkgn+zgmmV4P4ORmhOeXPBNXvMBpcqiwx/gEQQ==} 306 306 + dev: false 307 307 + 308 308 + /@atproto/xrpc-server@0.7.11: 309 309 + resolution: {integrity: sha512-kywMZMw2FbUFk0xBCtSI1mik+dc3uSvloNndI+N4X/+Qv1FGvoCRMi//9TqaSL13MFevTOynVoMVmaZbnaDG9A==} 310 310 + engines: {node: '>=18.7.0'} 273 311 dependencies: 274 274 - '@atproto/common': 0.4.6 275 275 - '@atproto/crypto': 0.4.2 276 276 - '@atproto/lexicon': 0.4.5 277 277 - '@atproto/xrpc': 0.6.6 312 312 + '@atproto/common': 0.4.8 313 313 + '@atproto/crypto': 0.4.4 314 314 + '@atproto/lexicon': 0.4.7 315 315 + '@atproto/xrpc': 0.6.9 278 316 cbor-x: 1.5.8 279 317 express: 4.18.2 280 318 http-errors: 2.0.0 ··· 289 327 - utf-8-validate 290 328 dev: false 291 329 292 292 - /@atproto/xrpc@0.6.6: 293 293 - resolution: {integrity: sha512-umXEYVMo9/pyIBoKmIAIi64RXDW9tSXY+wqztlQ6I2GZtjLfNZqmAWU+wADk3SxUe54mvjxxGyA4TtyGtDMfhA==} 330 330 + /@atproto/xrpc@0.6.9: 331 331 + resolution: {integrity: sha512-vQGA7++DYMNaHx3C7vEjT+2X6hYYLG7JNbBnDLWu0km1/1KYXgRkAz4h+FfYqg1mvzvIorHU7DAs5wevkJDDlw==} 294 332 dependencies: 295 295 - '@atproto/lexicon': 0.4.5 333 333 + '@atproto/lexicon': 0.4.7 296 334 zod: 3.23.8 297 335 dev: false 298 336 ··· 1364 1402 '@noble/hashes': 1.3.3 1365 1403 dev: false 1366 1404 1405 1405 + /@noble/curves@1.8.1: 1406 1406 + resolution: {integrity: sha512-warwspo+UYUPep0Q+vtdVB4Ugn8GGQj8iyB3gnRWsztmUHTI3S1nhdiWNsPUGL0vud7JlRRk1XEu7Lq1KGTnMQ==} 1407 1407 + engines: {node: ^14.21.3 || >=16} 1408 1408 + dependencies: 1409 1409 + '@noble/hashes': 1.7.1 1410 1410 + dev: false 1411 1411 + 1367 1412 /@noble/hashes@1.3.3: 1368 1413 resolution: {integrity: sha512-V7/fPHgl+jsVPXqqeOzT8egNj2iBIVt+ECeMMG8TdcnTikP3oaBtUVqpT/gYCR68aEBJSF+XbYUxStjbFMqIIA==} 1369 1414 engines: {node: '>= 16'} 1415 1415 + dev: false 1416 1416 + 1417 1417 + /@noble/hashes@1.7.1: 1418 1418 + resolution: {integrity: sha512-B8XBPsn4vT/KJAGqDzbwztd+6Yte3P4V7iafm24bxgDe/mlRuK6xmWPuCNrKt2vDafZ8MfJLlchDG/vYafQEjQ==} 1419 1419 + engines: {node: ^14.21.3 || >=16} 1370 1420 dev: false 1371 1421 1372 1422 /@noble/secp256k1@1.7.1: ··· 2258 2308 engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} 2259 2309 dev: false 2260 2310 2261 2261 - /detect-libc@2.0.2: 2262 2262 - resolution: {integrity: sha512-UX6sGumvvqSaXgdKGUsgZWqcUyIXZ/vZTrlRT/iobiKhGL0zL4d3osHj3uqllWJK+i+sixDS/3COVEOFbupFyw==} 2263 2263 - engines: {node: '>=8'} 2264 2264 - dev: false 2265 2265 - 2266 2311 /detect-libc@2.0.3: 2267 2312 resolution: {integrity: sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw==} 2268 2313 engines: {node: '>=8'} 2269 2314 dev: false 2270 2315 2271 2271 - /disposable-email-domains-js@1.8.0: 2272 2272 - resolution: {integrity: sha512-0lDlnSMXKSOXOIoERKdvCsy70LWwRHK2Pl2POZvlzm7Rihzl+WULTRv0bgGZSV50sZGlkW4fFbRL7f1LGcGq6g==} 2316 2316 + /disposable-email-domains-js@1.5.0: 2317 2317 + resolution: {integrity: sha512-L1cn+cZhKmxUwixH8n+n0HG+WbCz+LF4coyT6yMh930tpkD90ZWFx3A9dHIdFMVM745saaeNGYScIEstm3Y3yg==} 2273 2318 dev: false 2274 2319 2275 2320 /dom-serializer@1.4.1: ··· 2541 2586 resolution: {integrity: sha512-SyHy3T1v2NUXn29OsWdxmK6RwHD+vkj3v8en8AOBZ1wBQ/hCAQ5bAQTD02kW4W9tUp/3Qh6J8r9EvntiyCmOOw==} 2542 2587 dev: false 2543 2588 2544 2544 - /glob@10.3.10: 2545 2545 - resolution: {integrity: sha512-fa46+tv1Ak0UPK1TOy/pZrIybNNt4HCv7SDzwyfiOZkvZLEbjsZkJBPtDHVshZjbecAoAGSC20MjLDG/qr679g==} 2589 2589 + /glob@10.3.12: 2590 2590 + resolution: {integrity: sha512-TCNv8vJ+xz4QiqTpfOJA7HvYv+tNIRHKfUWw/q+v2jdgN4ebz+KY9tGx5J4rHP0o84mNP+ApH66HRX8us3Khqg==} 2546 2591 engines: {node: '>=16 || 14 >=14.17'} 2547 2592 hasBin: true 2548 2593 dependencies: 2549 2594 foreground-child: 3.1.1 2550 2595 jackspeak: 2.3.6 2551 2551 - minimatch: 9.0.3 2596 2596 + minimatch: 9.0.4 2552 2597 minipass: 7.0.4 2553 2553 - path-scurry: 1.10.1 2598 2598 + path-scurry: 1.10.2 2554 2599 dev: false 2555 2600 2556 2601 /gopd@1.0.1: ··· 2771 2816 engines: {node: 14 || >=16.14} 2772 2817 dev: false 2773 2818 2774 2774 - /lru-cache@6.0.0: 2775 2775 - resolution: {integrity: sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==} 2776 2776 - engines: {node: '>=10'} 2777 2777 - dependencies: 2778 2778 - yallist: 4.0.0 2779 2779 - dev: false 2780 2780 - 2781 2819 /media-typer@0.3.0: 2782 2820 resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==} 2783 2821 engines: {node: '>= 0.6'} ··· 2823 2861 resolution: {integrity: sha512-JIYlbt6g8i5jKfJ3xz7rF0LXmv2TkDxBLUkiBeZ7bAx4GnnNMr8xFpGnOxn6GhTEHx3SjRrZEoU+j04prX1ktg==} 2824 2862 dev: false 2825 2863 2826 2826 - /minimatch@9.0.3: 2827 2827 - resolution: {integrity: sha512-RHiac9mvaRw0x3AYRgDC1CxAP7HTcNrrECeA8YYJeWnpo+2Q5CegtZjaotWTWxDG3UeGA1coE05iH1mPjT/2mg==} 2864 2864 + /minimatch@9.0.4: 2865 2865 + resolution: {integrity: sha512-KqWh+VchfxcMNRAJjj2tnsSJdNbHsVgnkBhTNrW7AjVo6OvLtxw8zfT9oLw1JSohlFzJ8jCoTgaoXvJ+kHt6fw==} 2828 2866 engines: {node: '>=16 || 14 >=14.17'} 2829 2867 dependencies: 2830 2868 brace-expansion: 2.0.1 ··· 2876 2914 resolution: {integrity: sha512-uPEjtyh2tFEvWYt4Jw7McOD5FPcHkcxm/tHZc5PWaDB3JYq0rGFUbgaAK+CT5pYpQddBfsZVWI08OwoRfdfbcQ==} 2877 2915 engines: {node: '>=10'} 2878 2916 dependencies: 2879 2879 - semver: 7.6.0 2917 2917 + semver: 7.6.3 2880 2918 dev: false 2881 2919 2882 2920 /node-gyp-build-optional-packages@5.1.1: ··· 2884 2922 hasBin: true 2885 2923 requiresBuild: true 2886 2924 dependencies: 2887 2887 - detect-libc: 2.0.2 2925 2925 + detect-libc: 2.0.3 2888 2926 dev: false 2889 2927 optional: true 2890 2928 ··· 2973 3011 engines: {node: '>=8'} 2974 3012 dev: false 2975 3013 2976 2976 - /path-scurry@1.10.1: 2977 2977 - resolution: {integrity: sha512-MkhCqzzBEpPvxxQ71Md0b1Kk51W01lrYvlMzSUaIzNsODdd7mqhiimSZlr+VegAz5Z6Vzt9Xg2ttE//XBhH3EQ==} 3014 3014 + /path-scurry@1.10.2: 3015 3015 + resolution: {integrity: sha512-7xTavNy5RQXnsjANvVvMkEjvloOinkAjv/Z6Ildz9v2RinZ4SBKTWFOVRbaF8p0vpHnyjV/UwNDdKuUv6M5qcA==} 2978 3016 engines: {node: '>=16 || 14 >=14.17'} 2979 3017 dependencies: 2980 3018 lru-cache: 10.2.0 ··· 3032 3070 engines: {node: '>=10'} 3033 3071 hasBin: true 3034 3072 dependencies: 3035 3035 - detect-libc: 2.0.2 3073 3073 + detect-libc: 2.0.3 3036 3074 expand-template: 2.0.3 3037 3075 github-from-package: 0.0.0 3038 3076 minimist: 1.2.8 ··· 3198 3236 3199 3237 /semver-compare@1.0.0: 3200 3238 resolution: {integrity: sha512-YM3/ITh2MJ5MtzaM429anh+x2jiLVjqILF4m4oyQB18W7Ggea7BfqdH/wGMK7dDiMghv/6WG7znWMwUDzJiXow==} 3201 3201 - dev: false 3202 3202 - 3203 3203 - /semver@7.6.0: 3204 3204 - resolution: {integrity: sha512-EnwXhrlwXMk9gKu5/flx5sv/an57AkRplG3hTK68W7FRDN+k+OWBj65M7719OkA82XLBxrcX0KSHj+X5COhOVg==} 3205 3205 - engines: {node: '>=10'} 3206 3206 - hasBin: true 3207 3207 - dependencies: 3208 3208 - lru-cache: 6.0.0 3209 3239 dev: false 3210 3240 3211 3241 /semver@7.6.3: ··· 3604 3634 optional: true 3605 3635 utf-8-validate: 3606 3636 optional: true 3607 3607 - dev: false 3608 3608 - 3609 3609 - /yallist@4.0.0: 3610 3610 - resolution: {integrity: sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==} 3611 3637 dev: false 3612 3638 3613 3639 /zod@3.23.8: