build as plain js bundle without embedded bun

.gitignore

@@ -2,7 +2,10 @@
 .DS_Store
 
 # Docs
-public
+__pycache__
+docs/build
+/public
+js/public
 
 # JS
 node_modules
@@ -11,17 +14,24 @@ tsconfig.tsbuildinfo
 dist
 
 # JS CLI
-js/cli/proton-drive
+js/cli/release
 auth.txt
+auth-session.json
 cache*.sqlite
+events.json
+events.lock
+clientUid.json
 *.log
 *.bun-build
+config.json
+*.map
 
-# VS Code
+# IDEs
 .vs
+.vscode
+.idea
+*.swp
 
 # Tests
 tests/storage
-
-# Test reporter
 tests/test-results

LICENSE.md

@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2025 Proton AG
+Copyright (c) 2025-2026 Proton AG
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,11 +1,102 @@
 # Proton Drive SDK
 
-Copyright (c) 2025 Proton AG
+The Proton Drive SDK provides a high-level interface for interacting with Proton Drive. It is available in the following languages:
 
-This repository contains the Proton Drive SDK for JavaScript and C# (coming soon).
+- **TypeScript** — native SDK in [`js/sdk/`](./js/sdk/), available on npm as [`@protontech/drive-sdk`](https://www.npmjs.com/package/@protontech/drive-sdk). See [changelog](./js/CHANGELOG.md) for changes.
+- **C#** — native SDK in [`cs/sdk/`](./cs/sdk/). See [changelog](./cs/CHANGELOG.md) for changes.
+- **Kotlin** — bindings that wrap the C# SDK in [`kt/`](./kt/). See [changelog](./cs/CHANGELOG.md) for changes to the C# SDK.
+- **Swift** - bindings that wrap the C# SDK in [`swift/ProtonDriveSDK/`](./swift/ProtonDriveSDK/), available on github as [`sdk-swift`](https://github.com/ProtonDriveApps/sdk-swift). See [changelog](./cs/CHANGELOG.md) for changes to the C# SDK.
 
-At this point, the SDK is not ready for use. It is a work in progress.
+### Who this is for
 
-## Contributions
+| Audience | Expectations |
+| --- | --- |
+| **Proton first-party clients** | Primary focus today: this codebase is built for and validated alongside official Proton Drive apps. |
+| **Personal, non-commercial projects** | Allowed under [Guidelines](#usage-guidelines-for-personal-projects) below. Expect interface changes and the upcoming cryptographic migration until general availability. |
+| **Commercial or production third-party apps** | The SDK is not yet ready for third-party production use. |
 
-Contributions are not accepted at the moment.
+Using the SDK directly is still recommended over raw Drive API calls for any experimentation, so correctness, safety and rate-limit expectations stay aligned with first-party behavior. The SDK handles encryption and metadata processing, protecting uploaded data from corruption due to incorrect encryption or invalid metadata.
+
+## Current Status
+
+The SDK is actively being integrated into official Proton Drive clients. During this phase, the architecture and public interface may still change.
+
+**Upcoming cryptographic model change**:
+
+- **What changes:** Proton Drive will move to a new cryptographic model that improves performance, simplifies the architecture, and strengthens security.
+- **When:** Currently targeted for the **end of 2026/early 2027**. This window is an estimate and may shift; final timing and migration steps will be documented in this README and in the changelogs when they are finalized.
+- **What breaks:** Once the service uses the new model, any client that only implements the previous cryptography including older SDK releases will **not** interoperate until upgraded to a release that implements the new model.
+- **How to stay informed:** Watch this repository and read changelogs and README for migration notes and definitive dates.
+
+Once these changes are complete and the integration is stable, the SDK will be officially released for third-party use.
+
+Despite not being officially supported for third-party use at present, Proton strongly recommends integrating through this SDK rather than calling the Drive API directly. It is the same implementation used in Proton's first-party clients and is maintained to the same quality standards, even while the public interface continues to evolve. If you integrate without the SDK, you must still follow those guidelines; non-compliant clients may be rate-limited or blocked to protect Proton Drive and other users.
+
+## Usage Guidelines for Personal Projects
+
+The SDK may be used for personal, non-commercial projects. If you choose to build an application using Proton Drive, you **must** adhere to the requirements below.
+
+### Operational requirements
+
+These rules protect service availability and honest identification of clients. Rate limits are per session and user, thus third-party applications use the **same rate-limiting policy** as Proton first-party Drive clients.
+
+| Requirement | Description |
+| --- | --- |
+| **Use the SDK** | You are strongly encouraged to interact with Proton Drive through the SDK. If you make direct API calls, your application **must** implement the same correctness and safety guarantees as the SDK. Failing to use appropriate caching, event-based sync, parallelism limits, and exponential backoff may cause your application to be rate-limited to protect service availability. |
+| **Use official endpoints** | All HTTP requests must go to the official Proton Drive domain. Do not modify or proxy API endpoints to different domains. |
+| **Identify your application** | Set the `x-pm-appversion` HTTP header so it identifies your build honestly. Use the shape described below (for example, `external-drive-myapp@1.2.3-stable`). The value must accurately represent your application. Do not spoof or falsify this header. Third-party clients that seek to masquerade as official Proton first-party clients are forbidden and may stop working at any time. Customer support and development use the reported app version to troubleshoot requests; a **specific version may be blocked** if it is known to ship a serious bug. |
+| **Use event-based sync** | Synchronize data using Drive events. Do not poll the API or perform frequent recursive traversals of the file tree. Excessive polling or recursion may cause your application and your account to be rate-limited to protect service availability. |
+
+Use this pattern for `x-pm-appversion`:
+
+`external-drive-{name}@{semver}-{channel}+{suffix}` with optional SemVer build metadata `+{suffix}` (for example a short commit hash).
+
+- **`{name}`** — your project identifier using lowercase letters and underscores (e.g. `my_app`).
+- **`{semver}`** — `major.minor.patch` (e.g. `1.2.3`).
+- (optional) **`{channel}`** — one of `stable`, `beta`, or `alpha`.
+- (optional) **`+{suffix}`** — build metadata, for example a short commit hash (e.g. `+abc123f`).
+
+Examples:
+
+- `external-drive-myapp@1.2.3-stable`
+- `external-drive-my_app@2.0.0-beta`
+- `external-drive-photo_backup@1.0.0-alpha+abc123f`
+
+### Product and legal requirements
+
+These rules keep third-party apps distinguishable from official Proton products and transparent to users.
+
+| Requirement | Description |
+| --- | --- |
+| **No Proton branding** | Your application must not use Proton logos, trademarks, or design elements. It must be clearly distinguishable as an unofficial, third-party product. |
+| **Credential handling disclosure** | When you prompt a user for account details (including but not limited to username and password) your application must clearly state that it is a third-party application not officially supported by Proton. Suggested text: _This is a third-party application not officially supported by Proton._ |
+
+To protect the availability of Proton Drive and to properly safeguard the Proton customer experience, failure to comply with these requirements may result in your third-party application being limited or blocked from accessing Proton services. If you believe your third-party application has been improperly limited and/or blocked, please contact customer support on [proton.me/support/contact](https://proton.me/support/contact).
+
+## Scope and Limitations
+
+The SDK provides functionality for Proton Drive business logic only. It does **not** include:
+
+- Authentication or login flows
+- Session management
+- User address provider
+
+**Where to look first:** Official Proton Drive clients wire these pieces into the SDK; treat them as the living reference until this repository publishes standalone sample apps. Standalone integration support will be documented once the SDK reaches general availability.
+
+## Documentation
+
+We are preparing the documentation for the SDK. It will be available in the future.
+
+Until then, you can generate the code reference for the TypeScript SDK using the following command:
+
+```bash
+cd js/sdk && OUTPUT_PATH=./doc npm run generate-doc:interface
+```
+
+## License
+
+This project is licensed under the MIT License. See [LICENSE.md](./LICENSE.md) for details.
+
+> **Using Proton’s hosted services:** The MIT license governs **use of the source code in this repository** only. Access to **Proton’s hosted services** (including Proton Drive) remains subject to separate terms of service and operational policies. Integration rules and enforcement described in this README apply regardless of the OSS license.
+
+Copyright (c) 2026 Proton AG

SECURITY.md

@@ -1,3 +1,7 @@
 # Security
 
-TBD
+If you discover a security vulnerability in the Proton Drive SDK, please report it through our official bug bounty program:
+
+**[Proton Bug Bounty Program](https://proton.me/security/bug-bounty)**
+
+For general security inquiries, you can reach us at [security@proton.me](mailto:security@proton.me).

cs/.editorconfig

@@ -15,7 +15,6 @@ indent_style = space
 tab_width = 4
 
 # New line preferences
-end_of_line = crlf
 insert_final_newline = true
 
 #### .NET Coding Conventions ####
@@ -130,6 +129,8 @@ csharp_new_line_before_members_in_object_initializers = false
 csharp_new_line_before_open_brace = all
 csharp_new_line_between_query_expression_clauses = true
 
+roslynator_max_line_length = 160
+
 # Indentation preferences
 csharp_indent_block_contents = true
 csharp_indent_braces = false

cs/.gitignore

@@ -351,6 +351,11 @@ vcpkg_installed/
 build/output
 .vscode
 
+# DocFX
+docfx/api/
+docfx/_site/
+.tools/
+
 # macOS
 *.DS_Store
 .AppleDouble

cs/.globalconfig

@@ -3,10 +3,49 @@ is_global = true
 stylecop.layout.allowConsecutiveUsings = true
 stylecop.layout.allowDoWhileOnClosingBrace = true
 
+# IDE0001: Simplify Names
+dotnet_diagnostic.IDE0001.severity = warning
+
+# IDE0002: Simplify Member Access
+dotnet_diagnostic.IDE0002.severity = warning
+
+# IDE0003: Remove qualification
+dotnet_diagnostic.IDE0003.severity = warning
+
+# IDE0004: Remove Unnecessary Cast
+dotnet_diagnostic.IDE0004.severity = warning
+
+# IDE0005: Using directive is unnecessary.
+dotnet_diagnostic.IDE0005.severity = warning
+
+# IDE0007: Use var instead of explicit type
+dotnet_diagnostic.IDE0007.severity = warning
+
+# IDE0028: Use collection initializers or expressions
+dotnet_diagnostic.IDE0028.severity = warning
+
+# IDE0047: Remove unnecessary parentheses
+dotnet_diagnostic.IDE0047.severity = warning
+
+# CA1032: Implement standard exception constructors
 dotnet_diagnostic.CA1032.severity = warning
-dotnet_diagnostic.CA1711.severity = suggestion
+
+# CS1591: Missing XML comment for publicly visible type or member
+dotnet_diagnostic.CS1591.severity = none
+
+# CA1711: Identifiers should not have incorrect suffix
+dotnet_diagnostic.CA1711.severity = warning
+
+# CA1849: Call async methods when in an async method
+dotnet_diagnostic.CA1849.severity = warning
+
+# CA2000: Dispose objects before losing scope
 dotnet_diagnostic.CA2000.severity = suggestion
-dotnet_diagnostic.CA2201.severity = suggestion
+
+# CA2201: Do not raise reserved exception types
+dotnet_diagnostic.CA2201.severity = warning
+
+# CA2215: Dispose methods should call base class dispose
 dotnet_diagnostic.CA2215.severity = warning
 
 # StyleCop - Special
@@ -23,13 +62,13 @@ dotnet_diagnostic.SA1009.severity = suggestion
 # https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/ReadabilityRules.md
 
 dotnet_diagnostic.SA1101.severity = none
-dotnet_diagnostic.SA1200.severity = none
-dotnet_diagnostic.SA1216.severity = none
-dotnet_diagnostic.SA1217.severity = none
-dotnet_diagnostic.SA1413.severity = none
-dotnet_diagnostic.SA1502.severity = none
 dotnet_diagnostic.SA1516.severity = none
 
+# StyleCop - Naming
+# https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/NamingRules.md
+
+dotnet_diagnostic.SA1309.severity = none
+
 # StyleCop - Documentation
 # https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/DocumentationRules.md
 
@@ -77,70 +116,28 @@ dotnet_diagnostic.SA1648.severity = none
 
 dotnet_diagnostic.SX1101.severity = warning
 dotnet_diagnostic.SX1309.severity = warning
-dotnet_diagnostic.SA1309.severity = none
 
 # Roslynator
-dotnet_diagnostic.RCS1037.severity = none # Redundant with SA1028
-dotnet_diagnostic.RCS1194.severity = none # Redundant with CA1032
-
-# To discuss, remove to enable:
-
-# IDE0058: Expression value is never used
-dotnet_diagnostic.IDE0058.severity = none
-
-# CA1806: Do not ignore method results
-dotnet_diagnostic.CA1806.severity = none
-
-# SA1005: Single line comments should begin with single space
-dotnet_diagnostic.SA1005.severity = suggestion
-
-# SA1108: Block statements should not contain embedded comments
-dotnet_diagnostic.SA1108.severity = suggestion
-
-# SA1111: Closing parenthesis should be on line of last parameter
-dotnet_diagnostic.SA1111.severity = suggestion
-
-# SA1122: Use string.Empty for empty strings
-dotnet_diagnostic.SA1122.severity = suggestion
 
-# SA1127: Generic type constraints should be on their own line
-dotnet_diagnostic.SA1127.severity = suggestion
+# RCS0056: A line is too long
+dotnet_diagnostic.RCS0056.severity = warning
 
-# SA1128: Put constructor initializers on their own line
-dotnet_diagnostic.SA1128.severity = suggestion
-
-# SA1201: Elements should appear in the correct order
-dotnet_diagnostic.SA1201.severity = suggestion
-
-# SA1202: Elements should be ordered by access
-dotnet_diagnostic.SA1202.severity = suggestion
-
-# SA1204: Static elements should appear before instance elements
-dotnet_diagnostic.SA1204.severity = suggestion
-
-# SA1214: Readonly fields should appear before non-readonly fields
-dotnet_diagnostic.SA1214.severity = suggestion
-
-# SA1408: Conditional expressions should declare precedence
-dotnet_diagnostic.SA1408.severity = suggestion
-
-# SA1503: Braces should not be omitted
-dotnet_diagnostic.SA1503.severity = suggestion
+# RCS1037: Remove trailing white-space
+dotnet_diagnostic.RCS1037.severity = none # Redundant with SA1028
 
-# SA1512: Single-line comments should not be followed by blank line
-dotnet_diagnostic.SA1512.severity = suggestion
+# RCS1047: Non-asynchronous method name should not end with 'Async'
+dotnet_diagnostic.RCS1047.severity = warning
 
-# SA1515: Single-line comment should be preceded by blank line
-dotnet_diagnostic.SA1515.severity = suggestion
+# RCS1118: Mark local variable as const
+dotnet_diagnostic.RCS1118.severity = warning
 
-# SA1519: Braces should not be omitted from multi-line child statement
-dotnet_diagnostic.SA1519.severity = suggestion
+# RCS1090: Add parameter to exception constructor
+dotnet_diagnostic.RCS1194.severity = none # Redundant with CA1032
 
-# RCS1139: Add summary element to documentation comment.
-dotnet_diagnostic.RCS1139.severity = suggestion
+# Sonar
 
-# RCS1181: Convert comment to documentation comment.
-dotnet_diagnostic.RCS1181.severity = none
+# S1134: Track uses of "FIXME" tags
+dotnet_diagnostic.S1134.severity = suggestion
 
 # S1135: Complete the task associated to this 'TODO' comment
-dotnet_diagnostic.S1135.severity = suggestion
+dotnet_diagnostic.S1135.severity = suggestion