You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -32,12 +34,12 @@ The library uses [pino](https://github.com/pinojs/pino) for structured logging.
32
34
```
33
35
34
36
3.**Available log levels** (from most to least verbose):
35
-
-`trace` - Extremely detailed debugging information
36
-
-`debug` - Detailed debugging information
37
-
-`info` - General informational messages
38
-
-`warn` - Warning messages
39
-
-`error` - Error messages only
40
-
-`silent` - Disable all logging
37
+
-`trace` - Extremely detailed debugging information
38
+
-`debug` - Detailed debugging information
39
+
-`info` - General informational messages
40
+
-`warn` - Warning messages
41
+
-`error` - Error messages only
42
+
-`silent` - Disable all logging
41
43
42
44
## Documentation
43
45
@@ -49,12 +51,12 @@ The documentation can be generated automatically from the source files using [Ty
49
51
All unit tests are executed and their coverage is measured when using [vitest](https://vitest.dev/):
50
52
`pnpm test --coverage`
51
53
52
-
Style conventions are enforced using [Biome](https://biomejs.dev/): `biome check`
54
+
Style conventions are enforced using [oxlint](https://oxc.rs/docs/guide/usage/linter) and [oxfmt](https://oxc.rs/docs/guide/usage/formatter): `pnpm check`
53
55
54
56
## Versioning
55
57
56
58
The version number format for this library and the changes to the library associated with version number increments conform with [Semantic Versioning 2.0.0](https://semver.org/#semantic-versioning-200).
57
59
58
60
## Publishing
59
61
60
-
This library can be published as a [package on npmjs](https://www.npmjs.com/package/@nillion/nuc) via the GitHub Actions workflow.
62
+
This library can be published as a [package on npmjs](https://www.npmjs.com/package/@nillion/nuc) via the GitHub Actions workflow.
A Nuc (Nillion User Controlled) token is a type of capability-based authorisation token inspired by the UCAN specification. It grants specific permissions from a sender to a receiver. Three core claims define the actors in this relationship:
|**`iss`**|**Issuer (Sender)**| The principal who created and signed the token. |
22
22
|**`aud`**|**Audience (Receiver)**| The principal the token is addressed to. This is the only entity that can use (i.e., invoke or delegate) the token. |
23
23
|**`sub`**|**Subject**| The principal the token is "about". It represents the identity whose authority is being granted. This value must stay the same throughout a delegation chain. |
@@ -29,7 +29,7 @@ In a simple, two-party delegation, the `aud` and `sub` are often the same. When
29
29
This example demonstrates the primary workflow of creating delegation and invocation tokens:
0 commit comments