← Home

@ddd-ts/event-sourcing-inmemory

npm Repository Homepage
37
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
npm-metadata no-description AI (npm-metadata): Scoped monorepo package; no description is a stable pattern across all versions. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is consistent with monorepo automation; SLSA attestation corroborates legitimacy. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI/CD with Sigstore attestation; stable for this monorepo. ai
provenance missing-githead AI (provenance): Transition to GitHub Actions CI publish flow explains missing gitHead; SLSA provenance compensates. ai
bogus-package bogus-package AI (bogus-package): Tiny payload is expected for a monorepo sub-package re-export; not a spam indicator here. ai
phantom-deps phantom-dep:@ddd-ts/core AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for re-export packages. ai
phantom-deps phantom-dep:@ddd-ts/shape AI (phantom-deps): Same-org monorepo sibling; stable false positive. ai
phantom-deps phantom-dep:@ddd-ts/store-inmemory AI (phantom-deps): Same-org monorepo sibling; stable false positive. ai
phantom-deps phantom-dep:@ddd-ts/types AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, phantom-dep heuristic is a false positive here. ai

Versions (showing 37 of 37)

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

v0.0.49

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

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

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.