@ddd-ts/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped monorepo package @ddd-ts/core; name reflects DDD framework, not a cors typosquat. | ai | |
| dependencies | unvetted-dep:@ddd-ts/shape | AI (dependencies): Sibling package in the same ddd-ts monorepo; expected co-versioned dependency. | ai | |
| dependencies | unvetted-dep:@ddd-ts/types | AI (dependencies): Sibling package in the same ddd-ts monorepo; expected co-versioned dependency. | ai | |
| dependencies | unvetted-dep:@ddd-ts/traits | AI (dependencies): Sibling package in the same ddd-ts monorepo; expected co-versioned dependency. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.45 | 4 / 4 | |
| 0.0.42 | 4 / 4 | |
| 0.0.38 | 4 / 4 | |
| 0.0.36 | 4 / 4 | |
| 0.0.35 | 4 / 4 | |
| 0.0.34 | 4 / 4 | |
| 0.0.33 | 4 / 4 | |
| 0.0.32 | 4 / 4 | |
| 0.0.31 | 4 / 4 | |
| 0.0.30 | 4 / 4 | |
| 0.0.29 | 4 / 4 | |
| 0.0.28 | 4 / 4 |
v0.0.42
2 findingsPackage name '@ddd-ts/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.36
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.