← Home

@dxos/credentials

npm Repository Homepage

DXOS Credentials

11
Versions
MIT
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 org migrated publishing from dxos-bot to GitHub Actions CI; SLSA attestation confirms legitimate CI provenance. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with org-level CI migration; no external takeover indicators. ai
phantom-deps phantom-dep:@dxos/keyring AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly through bundled output. ai

Versions (showing 11 of 11)

Version Deps Published
0.10.0 13 / 0
0.9.0 13 / 0
0.8.3 13 / 1
0.8.2 13 / 1
0.8.1 13 / 1
0.8.0 13 / 1
0.7.4 13 / 1
0.7.3 13 / 1
0.7.2 13 / 1
0.7.1 13 / 1
0.7.0 13 / 1

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.