← Home

@dxos/feed-store

A consistent store for hypercore feeds.

31
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 migrated publishing to GitHub Actions CI with SLSA attestation; this is the expected new publisher for all @dxos/* packages. ai
dependencies unvetted-dep:@dxos/vendor-hypercore AI (dependencies): Scoped @dxos monorepo package at matching 0.9.0 version; consistent with internal refactor, not a third-party injection. ai
dependencies unvetted-dep:@dxos/log AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/keys AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/util AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/async AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/crypto AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
provenance no-provenance AI (provenance): Established dxos monorepo package; provenance not used across their releases. ai
dependencies unvetted-dep:@dxos/keyring AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/hypercore AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/codec-protobuf AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/random-access-storage AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:@dxos/context AI (dependencies): Sibling @dxos monorepo package at matching version; not an independent risk. ai
dependencies unvetted-dep:streamx AI (dependencies): streamx is a well-known stream library; stable dependency for this package. ai

Versions (showing 31 of 31)

Version Deps Published
0.9.0 17 / 3
0.8.3 16 / 3
0.8.2 16 / 3
0.8.1 16 / 3
0.8.0 16 / 3
0.7.4 16 / 3
0.7.3 16 / 3
0.7.2 16 / 3
0.7.1 16 / 3
0.7.0 16 / 3
0.6.13 16 / 3
0.6.12 16 / 3
0.6.11 16 / 3
0.6.10 16 / 3
0.6.9 16 / 3
0.6.8 16 / 3
0.6.7 16 / 3
0.6.6 16 / 3
0.6.5 16 / 3
0.6.4 16 / 3
0.6.3 16 / 3
0.6.2 16 / 3
0.6.1 16 / 3
0.6.0 16 / 3
0.5.8 16 / 3
0.5.7 16 / 3
0.5.6 16 / 3
0.5.5 16 / 3
0.5.4 16 / 3
0.5.3 17 / 3
0.5.2 17 / 3

v0.8.1

1 finding
INFO No provenance attestation provenance

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

v0.8.0

1 finding
INFO No provenance attestation provenance

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

v0.7.4

1 finding
INFO No provenance attestation provenance

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

v0.7.3

1 finding
INFO No provenance attestation provenance

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

v0.7.2

1 finding
INFO No provenance attestation provenance

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

v0.7.1

1 finding
INFO No provenance attestation provenance

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

v0.7.0

1 finding
INFO No provenance attestation provenance

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

v0.6.13

1 finding
INFO No provenance attestation provenance

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

v0.6.12

1 finding
INFO No provenance attestation provenance

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

v0.6.11

1 finding
INFO No provenance attestation provenance

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

v0.6.10

1 finding
INFO No provenance attestation provenance

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

v0.6.9

1 finding
INFO No provenance attestation provenance

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

v0.6.8

1 finding
INFO No provenance attestation provenance

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

v0.6.7

1 finding
INFO No provenance attestation provenance

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

v0.6.6

1 finding
INFO No provenance attestation provenance

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

v0.6.5

1 finding
INFO No provenance attestation provenance

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

v0.6.4

1 finding
INFO No provenance attestation provenance

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

v0.6.3

1 finding
INFO No provenance attestation provenance

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

v0.6.2

1 finding
INFO No provenance attestation provenance

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

v0.6.1

1 finding
INFO No provenance attestation provenance

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

v0.6.0

1 finding
INFO No provenance attestation provenance

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

v0.5.8

1 finding
INFO No provenance attestation provenance

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

v0.5.7

1 finding
INFO No provenance attestation provenance

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

v0.5.6

1 finding
INFO No provenance attestation provenance

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

v0.5.5

1 finding
INFO No provenance attestation provenance

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

v0.5.4

1 finding
INFO No provenance attestation provenance

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

v0.5.3

1 finding
INFO No provenance attestation provenance

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

v0.5.2

1 finding
INFO No provenance attestation provenance

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