@ddd-ts/event-sourcing-firestore
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ddd-ts/core | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package. | ai | |
| dependencies | unvetted-dep:@ddd-ts/shape | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package. | ai | |
| dependencies | unvetted-dep:@ddd-ts/types | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package. | ai | |
| dependencies | unvetted-dep:@ddd-ts/traits | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package. | ai | |
| dependencies | unvetted-dep:@ddd-ts/store-firestore | AI (dependencies): Same-org monorepo sibling; version-pinned alongside this package. | ai | |
| phantom-deps | phantom-dep:@ddd-ts/types | AI (phantom-deps): Same-org sibling; may be transitively used or type-only import not detected. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.45 | 7 / 5 | |
| 0.0.35 | 7 / 5 | |
| 0.0.34 | 7 / 5 | |
| 0.0.33 | 7 / 5 | |
| 0.0.32 | 5 / 5 | |
| 0.0.31 | 5 / 5 | |
| 0.0.30 | 5 / 5 | |
| 0.0.29 | 5 / 5 | |
| 0.0.28 | 5 / 5 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.