@dxos/util
Temporary bucket for misc functions, which should graduate into separate packages.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): DXOS migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate org-wide transition. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is in a utility function for JSON-encoded Uint8Array serialization, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @dxos/util is a scoped monorepo utility package with no relation to uuid; Levenshtein match is coincidental. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex encode/decode helpers for Uint8Array conversion; no obfuscation or payload hiding. | ai | |
| dependencies | unvetted-dep:@dxos/keys | AI (dependencies): Sibling DXOS monorepo package at matching version; stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 5 / 1 | |
| 0.9.0 | 5 / 1 | |
| 0.8.3 | 6 / 3 | |
| 0.8.2 | 6 / 3 | |
| 0.8.1 | 4 / 1 | |
| 0.8.0 | 4 / 1 | |
| 0.7.4 | 4 / 1 | |
| 0.7.3 | 4 / 1 | |
| 0.7.2 | 4 / 1 | |
| 0.7.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.13 | 6 / 1 | |
| 0.6.12 | 6 / 1 | |
| 0.6.11 | 6 / 1 | |
| 0.6.10 | 6 / 1 | |
| 0.6.9 | 6 / 1 | |
| 0.6.8 | 6 / 1 | |
| 0.6.7 | 6 / 1 | |
| 0.6.6 | 6 / 1 | |
| 0.6.5 | 6 / 1 | |
| 0.6.4 | 6 / 1 | |
| 0.6.3 | 6 / 1 | |
| 0.6.2 | 6 / 1 | |
| 0.6.1 | 6 / 1 | |
| 0.6.0 | 6 / 1 | |
| 0.5.8 | 4 / 1 | |
| 0.5.7 | 4 / 1 | |
| 0.5.6 | 4 / 1 | |
| 0.5.5 | 4 / 1 | |
| 0.5.4 | 4 / 1 | |
| 0.5.3 | 4 / 1 | |
| 0.5.2 | 4 / 1 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.