← Home

@dxos/test-utils

Test utilities

11
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

richburdonmarik_dwittjosiahdxos-botmykola-vrmchk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from dxos-bot to GitHub Actions CI is a legitimate automation change, backed by SLSA provenance attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with org-level CI migration; SLSA attestation confirms legitimate publish pipeline. ai
bogus-package bogus-package AI (bogus-package): Internal utility package from DXOS monorepo; sparse README/keywords are expected for org-internal tooling. ai

Versions (showing 11 of 11)

Version Deps Published
0.10.0 4 / 0
0.9.0 4 / 0
0.8.3 5 / 0
0.8.2 5 / 0
0.8.1 5 / 0
0.8.0 6 / 0
0.7.4 6 / 0
0.7.3 6 / 0
0.7.2 6 / 0
0.7.1 6 / 0
0.7.0 6 / 0

v0.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published 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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.