@dxos/keyboard
Keyboard bindings
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): DXOS monorepo migrated CI publisher from dxos-bot to GitHub Actions; SLSA attestation confirms legitimate CI origin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal aligns with org-level CI migration; no malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): DXOS org packages consistently lack provenance attestation; not a risk indicator for this publisher. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 3 / 5 | |
| 0.9.0 | 3 / 5 | |
| 0.8.3 | 3 / 5 | |
| 0.8.2 | 3 / 5 | |
| 0.8.1 | 3 / 5 | |
| 0.8.0 | 3 / 5 | |
| 0.7.4 | 3 / 5 | |
| 0.7.3 | 3 / 5 | |
| 0.7.2 | 3 / 5 | |
| 0.7.1 | 3 / 5 | |
| 0.7.0 | 3 / 5 | |
| 0.6.13 | 3 / 5 | |
| 0.6.12 | 3 / 5 | |
| 0.6.11 | 3 / 5 | |
| 0.6.10 | 3 / 5 | |
| 0.6.9 | 3 / 5 | |
| 0.6.8 | 3 / 5 | |
| 0.6.7 | 3 / 5 | |
| 0.6.6 | 3 / 5 | |
| 0.6.5 | 3 / 5 | |
| 0.6.4 | 3 / 5 | |
| 0.6.3 | 3 / 5 | |
| 0.6.2 | 3 / 5 | |
| 0.6.1 | 3 / 5 | |
| 0.6.0 | 3 / 5 | |
| 0.5.8 | 3 / 5 | |
| 0.5.7 | 3 / 5 | |
| 0.5.6 | 3 / 5 | |
| 0.5.5 | 3 / 5 | |
| 0.5.4 | 3 / 5 | |
| 0.5.3 | 3 / 5 | |
| 0.5.2 | 3 / 5 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.