@ekairos/domain
Domain-first TypeScript primitives for InstantDB: schema composition, typed actions, and runtime execution.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.22.3 | 2 / 6 | |
| 1.22.2 | 2 / 6 | |
| 1.22.1 | 2 / 6 | |
| 1.22.0 | 2 / 6 | |
| 1.21.101 | 2 / 6 | |
| 1.21.0 | 1 / 3 | |
| 1.19.0 | 1 / 3 | |
| 1.18.0 | 1 / 3 | |
| 1.17.0 | 1 / 3 | |
| 1.16.9 | 1 / 3 | |
| 1.16.8 | 1 / 3 | |
| 1.16.6 | 1 / 3 | |
| 1.16.5 | 1 / 3 | |
| 1.16.0 | 1 / 3 | |
| 1.15.0 | 1 / 3 | |
| 1.12.0 | 1 / 3 | |
| 1.11.0 | 1 / 3 | |
| 1.10.0 | 1 / 3 | |
| 1.9.0 | 1 / 3 | |
| 1.8.3 | 1 / 3 | |
| 1.8.2 | 1 / 3 | |
| 1.6.1 | 1 / 3 | |
| 1.6.0 | 1 / 3 |
v1.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.101
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.