@syncropel/config
JSON Schema definitions + TypeScript types for the Syncropel daemon's configuration records. Use with any JSON Schema validator to lint routing rules, triggers, fold rules, health checks, AITL rules, and permission rules before applying them via `th_engin
8
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
dpwanjala
Keywords
syncropelprotocolconfigjson-schemavalidation
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build script change in this version plausibly explains missing gitHead; no other risk signals present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ajv is a canonical JSON Schema validator; its addition is consistent with this package's schema-validation purpose. | ai | |
| provenance | no-provenance | AI (provenance): Young package without CI provenance setup; no malicious signals present to elevate this. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 1 / 3 | |
| 0.14.0 | 1 / 3 | |
| 0.13.1 | 1 / 3 | |
| 0.13.0 | 0 / 4 | |
| 0.12.0 | 0 / 4 | |
| 0.10.0 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.0 | 0 / 4 |
v0.15.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.