← Home

@dxos/config

npm
17
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mykola-vrmchkdxos-botgcolottisebikap-gm2richburdonegorgripasovmarik_drzad-pyivladmeschzarconontolwittjosiah

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): DXOS monorepo migrated publishing from dxos-bot to GitHub Actions CI; SLSA attestation confirms legitimate pipeline. ai
semgrep semgrep:env-bulk-read AI (semgrep): Config library intentionally reads process.env; filtered to DX_ prefix or explicit allowlist — expected pattern for this package. ai
phantom-deps phantom-dep:@dxos/node-std AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic fires on indirect/conditional imports common in this monorepo. ai

Versions (showing 17 of 17)

Version Deps Published
0.10.0 14 / 3
0.9.0 14 / 3
0.8.3 11 / 4
0.8.2 11 / 4
0.8.1 11 / 4
0.8.0 11 / 4
0.7.4 11 / 4
0.7.3 11 / 4
0.7.2 11 / 4
0.7.1 11 / 4
0.7.0 11 / 4
0.6.13 11 / 4
0.6.12 11 / 4
0.6.11 11 / 4
0.6.10 11 / 4
0.6.9 11 / 4
0.6.8 11 / 4

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.13

1 finding
LOW No provenance attestation provenance

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

v0.6.12

1 finding
LOW No provenance attestation provenance

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

v0.6.11

1 finding
LOW No provenance attestation provenance

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

v0.6.10

1 finding
LOW No provenance attestation provenance

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

v0.6.9

1 finding
LOW No provenance attestation provenance

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

v0.6.8

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.