@ddd-ts/event-sourcing-esdb
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| phantom-deps | phantom-dep:@eventstore/db-client | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package with 276 versions; empty dist is a build artifact pattern, not spam. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.45 | 2 / 6 | |
| 0.0.44 | 2 / 6 | |
| 0.0.39 | 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 |
v0.0.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.