← Home

@ddd-ts/event-sourcing-esdb

npm Repository Homepage
41
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

arthur-fontaineaetherallyooooomi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ddd-ts/event-sourcing AI (dependencies): Sibling package from same trusted publisher/monorepo. ai
provenance missing-githead AI (provenance): Monorepo CI publish quirk; provenance direction unchanged, still attested. ai
publish-pattern rapid-publish AI (publish-pattern): Monorepo lockstep versioning causes rapid sequential publishes. ai
npm-metadata no-description AI (npm-metadata): Consistent across all 278 versions of this monorepo package; not a malware signal. ai
phantom-deps phantom-dep:@ddd-ts/core AI (phantom-deps): Same-org monorepo sibling; phantom-dep false positive for peer/type-only usage. ai
bogus-package bogus-package AI (bogus-package): Monorepo package with 276 versions; empty dist is a build artifact pattern, not spam. ai
phantom-deps phantom-dep:@eventstore/db-client AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. ai

Versions (showing 41 of 41)

Version Deps Published
0.0.49 2 / 6
0.0.48 2 / 6
0.0.47 2 / 6
0.0.46 2 / 6
0.0.45 2 / 6
0.0.44 2 / 6
0.0.43 2 / 6
0.0.42 2 / 6
0.0.41 2 / 6
0.0.40 2 / 6
0.0.39 2 / 6
0.0.38 2 / 6
0.0.37 2 / 6
0.0.36 2 / 6
0.0.35 2 / 6
0.0.34 2 / 6
0.0.33 2 / 6
0.0.32 2 / 6
0.0.31 2 / 6
0.0.30 2 / 6
0.0.29 2 / 6
0.0.28 2 / 6
0.0.27 2 / 6
0.0.26 2 / 6
0.0.25 2 / 6
0.0.24 2 / 6
0.0.23 2 / 6
0.0.22 2 / 6
0.0.21 2 / 6
0.0.20 2 / 6
0.0.19 2 / 6
0.0.18 2 / 6
0.0.17 2 / 6
0.0.16 2 / 6
0.0.15 2 / 6
0.0.14 2 / 6
0.0.13 2 / 6
0.0.12 2 / 6
0.0.11 2 / 6
0.0.10 2 / 6
0.0.9 2 / 6

v0.0.49

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

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

1 finding
LOW No provenance attestation provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

1 finding
LOW No provenance attestation provenance

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

v0.0.24

1 finding
LOW No provenance attestation provenance

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

v0.0.23

1 finding
LOW No provenance attestation provenance

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

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

1 finding
LOW No provenance attestation provenance

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

v0.0.17

1 finding
LOW No provenance attestation provenance

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

v0.0.16

1 finding
LOW No provenance attestation provenance

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

v0.0.15

1 finding
LOW No provenance attestation provenance

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

v0.0.14

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

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

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

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

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

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.