@atproto/pds
Reference implementation of atproto Personal Data Server (PDS)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @atproto/did is a first-party same-org dependency; no supply chain risk. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large atproto monorepo; incremental source file additions are expected across minor releases. | ai | |
| dependencies | unvetted-dep:@did-plc/lib | AI (dependencies): DID PLC library from the same Bluesky ecosystem; expected dependency for a PDS. | ai | |
| dependencies | unvetted-dep:@atproto/xrpc-server | AI (dependencies): Same org scope (@atproto); sibling package in the official monorepo. | ai | |
| dependencies | unvetted-dep:nodemailer-html-to-text | AI (dependencies): Email utility dep; expected for PDS email functionality. | ai | |
| dependencies | unvetted-dep:@atproto-labs/xrpc-utils | AI (dependencies): Same org scope (@atproto-labs); sibling package in the official monorepo. | ai | |
| dependencies | unvetted-dep:@atproto-labs/simple-store-redis | AI (dependencies): Same org scope (@atproto-labs); sibling package in the official monorepo. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): Legitimate templating dep for email/HTML in the official atproto PDS; stable usage across versions. | ai | |
| dependencies | unvetted-dep:key-encoder | AI (dependencies): Crypto key encoding utility; expected in a PDS implementation handling cryptographic keys. | ai | |
| dependencies | unvetted-dep:@atproto/aws | AI (dependencies): Same org scope (@atproto); sibling package in the official monorepo. | ai | |
| phantom-deps | phantom-dep:@atproto/xrpc | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is unreliable for monorepo packages. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @atproto/pds; levenshtein match to bare 'pg' is a false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is standard HTTP Basic Auth credential parsing, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @atproto/pds; levenshtein match to bare 'qs' is a false positive. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.5.21 | 45 / 17 | |
| 0.5.20 | 45 / 17 | |
| 0.5.19 | 45 / 17 | |
| 0.5.18 | 45 / 17 | |
| 0.5.17 | 45 / 17 | |
| 0.5.16 | 45 / 17 | |
| 0.5.15 | 45 / 17 | |
| 0.5.1 | 45 / 19 | |
| 0.5.0 | 44 / 19 | |
| 0.4.225 | 44 / 19 | |
| 0.4.224 | 44 / 19 | |
| 0.4.223 | 44 / 18 | |
| 0.4.222 | 44 / 18 | |
| 0.4.221 | 44 / 18 | |
| 0.4.220 | 44 / 19 | |
| 0.4.219 | 44 / 19 | |
| 0.4.218 | 44 / 19 | |
| 0.4.217 | 44 / 19 | |
| 0.4.216 | 46 / 19 | |
| 0.4.215 | 46 / 19 | |
| 0.4.214 | 46 / 19 | |
| 0.4.213 | 46 / 19 | |
| 0.4.212 | 46 / 19 | |
| 0.4.211 | 46 / 19 | |
| 0.4.210 | 46 / 19 | |
| 0.4.209 | 46 / 19 | |
| 0.4.208 | 46 / 19 | |
| 0.4.207 | 46 / 19 | |
| 0.4.206 | 46 / 19 | |
| 0.4.205 | 46 / 19 | |
| 0.4.204 | 47 / 19 | |
| 0.4.203 | 47 / 19 | |
| 0.4.202 | 47 / 19 | |
| 0.4.201 | 47 / 19 | |
| 0.4.200 | 47 / 19 | |
| 0.4.199 | 47 / 19 | |
| 0.4.198 | 47 / 19 | |
| 0.4.197 | 47 / 19 | |
| 0.4.196 | 48 / 19 | |
| 0.4.195 | 48 / 19 | |
| 0.4.194 | 46 / 19 | |
| 0.4.193 | 46 / 19 | |
| 0.4.192 | 46 / 19 | |
| 0.4.61 | 39 / 18 | |
| 0.4.60 | 39 / 18 | |
| 0.4.55 | 38 / 18 | |
| 0.4.54 | 38 / 18 | |
| 0.4.53 | 38 / 18 | |
| 0.4.52 | 38 / 18 | |
| 0.4.51 | 38 / 18 | |
| 0.4.50 | 38 / 18 | |
| 0.4.49 | 38 / 18 | |
| 0.4.48 | 38 / 18 | |
| 0.4.47 | 38 / 18 | |
| 0.4.46 | 38 / 18 | |
| 0.4.45 | 38 / 18 | |
| 0.4.44 | 38 / 18 | |
| 0.4.43 | 38 / 18 | |
| 0.4.42 | 38 / 18 | |
| 0.4.41 | 38 / 18 | |
| 0.4.40 | 38 / 18 | |
| 0.4.39 | 38 / 18 | |
| 0.4.38 | 38 / 18 | |
| 0.4.37 | 38 / 18 | |
| 0.4.36 | 38 / 18 | |
| 0.4.35 | 38 / 18 | |
| 0.4.34 | 36 / 18 | |
| 0.4.33 | 36 / 18 | |
| 0.4.32 | 36 / 18 | |
| 0.4.31 | 36 / 18 | |
| 0.4.30 | 36 / 18 | |
| 0.4.29 | 36 / 18 | |
| 0.4.28 | 36 / 18 | |
| 0.4.27 | 36 / 18 | |
| 0.4.26 | 36 / 18 | |
| 0.4.25 | 36 / 18 | |
| 0.4.24 | 36 / 18 | |
| 0.4.23 | 36 / 18 | |
| 0.4.22 | 36 / 18 | |
| 0.4.21 | 36 / 18 | |
| 0.4.20 | 36 / 18 | |
| 0.4.19 | 36 / 18 |
v0.5.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.217
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.216
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.215
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.214
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.213
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.212
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.211
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.210
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.209
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.208
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.207
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.206
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.205
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.204
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.203
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.202
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (devinivy) on 2026-01-06, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.4.201
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (devinivy) on 2026-01-02, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.4.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinivy) than the most recent previously approved version (dholms) on 2024-06-18, but devinivy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.