← Home

@dxos/teleport-extension-automerge-replicator

npm Repository Homepage
3
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): DXOS monorepo migrated publishing to GitHub Actions CI with SLSA attestation; consistent with legitimate pipeline change. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with org-level CI/CD transition; no malicious indicators present. ai
npm-metadata no-description AI (npm-metadata): Monorepo package; empty description is a consistent pattern across @dxos org packages. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals present for this org. ai
phantom-deps phantom-dep:@dxos/node-std AI (phantom-deps): Same-org sibling dep; likely used indirectly via platform shims in this monorepo package. ai

Versions (showing 3 of 3)

Version Deps Published
0.9.0 8 / 0
0.8.3 8 / 0
0.8.2 8 / 0

v0.9.0

2 findings
HIGH Publisher changed: dxos-bot → GitHub Actions (on 2026-06-15) provenance

This version was published by a different npm account than previous versions on 2026-06-15. This could indicate a legitimate maintainer transition or an account compromise.

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.3

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.

v0.8.2

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.