@byok-sdk/core 0.28.2 → 0.29.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -0
- package/dist/sealed-payload/index.d.ts +15 -0
- package/dist/sealed-payload/index.js +1048 -0
- package/dist/sealed-payload/index.js.map +1 -0
- package/dist/sealed-payload/member-chain.d.ts +58 -0
- package/dist/sealed-payload/primitives.d.ts +53 -0
- package/dist/sealed-payload/scope-key.d.ts +91 -0
- package/dist/sealed-payload/sealed-content.d.ts +185 -0
- package/package.json +5 -1
package/README.md
CHANGED
|
@@ -15,6 +15,17 @@ row, and consumes the JTI through an injected `DeviceAssertionReplayAuthority`.
|
|
|
15
15
|
hosted production composition must inject durable atomic storage. The assertion
|
|
16
16
|
authorizes one exchange only and is not a connector session or refresh token.
|
|
17
17
|
|
|
18
|
+
Sealed payload v1 (#654) has its own subpath, so the root entry does not grow:
|
|
19
|
+
|
|
20
|
+
```ts
|
|
21
|
+
import { openSealedContent, sealContent } from '@byok-sdk/core/sealed-payload';
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
It seals and opens one category of a payload, wraps a scope key to one member
|
|
25
|
+
as a signed key package, and signs and verifies one member chain entry. The
|
|
26
|
+
receivers return a typed failure for hostile input and do not throw. The wire
|
|
27
|
+
does not carry sealed content yet; later #654 slices add it.
|
|
28
|
+
|
|
18
29
|
MIT licensed. Node.js 24.22.1 or newer.
|
|
19
30
|
|
|
20
31
|
Runtime dependencies and size budgets: [entry dependency contract](../../README.md#entry-dependencies).
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* `@byok-sdk/core/sealed-payload` — sealed payload v1 (#654): sealed contents,
|
|
3
|
+
* scope keys and key packages, and member chain entries. The browser, the
|
|
4
|
+
* device and the hosted Host run this same WebCrypto code.
|
|
5
|
+
*
|
|
6
|
+
* It is a subpath, not part of the package root, so the root bundle and every
|
|
7
|
+
* closure that imports the root do not grow. Only a consumer that seals or
|
|
8
|
+
* opens content imports it.
|
|
9
|
+
*/
|
|
10
|
+
export { SEALED_CATEGORIES, SEALED_CONTENT_SUITE, SEALED_CONTENT_VERSION, SEALED_DIRECTIONS, SealedContentHeaderV1Schema, openSealedContent, sealContent, } from './sealed-content';
|
|
11
|
+
export type { OpenSealedContentInput, SealContentInput, SealedBinding, SealedCategory, SealedContent, SealedContentHeaderV1, SealedContentOpenFailure, SealedContentOpenResult, SealedDirection, SealedScopePolicy, } from './sealed-content';
|
|
12
|
+
export { deriveScopeKeyId, generateScopeKey, openScopeKeyPackage, sealScopeKeyPackage } from './scope-key';
|
|
13
|
+
export type { OpenScopeKeyPackageInput, ScopeKeyPackageOpenResult, ScopeKeyPackageV1, SealScopeKeyPackageInput, } from './scope-key';
|
|
14
|
+
export { MEMBER_CHAIN_OPS, deriveMemberId, memberChainEntryHash, signMemberChainEntry, verifyMemberChainEntry, } from './member-chain';
|
|
15
|
+
export type { MemberChainEntryV1, MemberChainEntryVerifyResult, MemberChainOp, UnsignedMemberChainEntryV1, } from './member-chain';
|