@complyedge/sdk 0.2.2 → 0.2.3
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/CHANGELOG.md +16 -0
- package/README.md +12 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,21 @@ numbers are deliberately not kept level between the two — they are separate
|
|
|
14
14
|
implementations with different capability surfaces, so matching numbers would
|
|
15
15
|
imply a parity that does not exist.
|
|
16
16
|
|
|
17
|
+
## [0.2.3] - 2026-08-20
|
|
18
|
+
|
|
19
|
+
### Added
|
|
20
|
+
- Package-map capability table (CE-vs-CE only): offline vs hosted, Rego/OPA,
|
|
21
|
+
Article 12, bundled corpus, ESM/CJS, MCP. Named competitor comparisons stay
|
|
22
|
+
gated — they need an explicit messaging decision against the no-first/only
|
|
23
|
+
doctrine.
|
|
24
|
+
|
|
25
|
+
### Fixed
|
|
26
|
+
- Release-path fact: publishes still use `NPM_TOKEN`. The 0.2.2 changelog
|
|
27
|
+
entry that claimed OIDC Trusted Publishing described an attempt that was
|
|
28
|
+
reverted (`repository.url` points at the public repo while workflows run in
|
|
29
|
+
the private platform). Provenance remains unavailable until that layout
|
|
30
|
+
changes (G1a).
|
|
31
|
+
|
|
17
32
|
## [0.2.2] - 2026-08-20
|
|
18
33
|
|
|
19
34
|
### Changed
|
|
@@ -51,5 +66,6 @@ imply a parity that does not exist.
|
|
|
51
66
|
|
|
52
67
|
Released before this changelog existed. See the repository history.
|
|
53
68
|
|
|
69
|
+
[0.2.3]: https://www.npmjs.com/package/@complyedge/sdk/v/0.2.3
|
|
54
70
|
[0.2.2]: https://www.npmjs.com/package/@complyedge/sdk/v/0.2.2
|
|
55
71
|
[0.2.1]: https://www.npmjs.com/package/@complyedge/sdk/v/0.2.1
|
package/README.md
CHANGED
|
@@ -25,6 +25,18 @@ The SDK works in both ESM and CommonJS projects; no bundler-specific setup is re
|
|
|
25
25
|
- [`complyedge` on PyPI](https://pypi.org/project/complyedge/) is the Python SDK with the same enforcement API.
|
|
26
26
|
- [Documentation](https://www.complyedge.io/docs) covers the hosted API; the [trust portal](https://trust.complyedge.io) covers security and reliability information.
|
|
27
27
|
|
|
28
|
+
| | `@complyedge/sdk` | `trustlint` | `@complyedge/mcp` |
|
|
29
|
+
|---|:-:|:-:|:-:|
|
|
30
|
+
| Runs offline, no API key | ✗ | ✓ | ✓ |
|
|
31
|
+
| Rego / OPA evaluation | ✓ | ✗ | ✗ |
|
|
32
|
+
| Article 12 audit trail | ✓ | ✗ | ✗ |
|
|
33
|
+
| Bundled 64-rule corpus | ✗ | ✓ | ✓ |
|
|
34
|
+
| Temporal / effective-date rules | ✗ | ✗ | ✗ |
|
|
35
|
+
| ESM + CommonJS | ✓ | ✓ | ESM only |
|
|
36
|
+
| MCP host integration | ✗ | ✗ | ✓ |
|
|
37
|
+
|
|
38
|
+
Temporal / effective-date evaluation lives in the Python engine only. A shared version number across npm and PyPI is not a parity claim.
|
|
39
|
+
|
|
28
40
|
## Version policy
|
|
29
41
|
|
|
30
42
|
The TypeScript SDK and Python `complyedge` package have independent semantic versions. A version number does not imply feature parity across languages; each release documents and tests its own supported API surface.
|
package/package.json
CHANGED