@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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo lockstep publish via CI; no behavioral change, low-risk metadata gap. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo packages publish together in quick succession; expected pattern. | ai | |
| 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 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.0.49 | 4 / 4 | |
| 0.0.48 | 4 / 4 | |
| 0.0.47 | 4 / 4 | |
| 0.0.46 | 4 / 4 | |
| 0.0.45 | 4 / 4 | |
| 0.0.44 | 4 / 4 | |
| 0.0.43 | 4 / 4 | |
| 0.0.42 | 4 / 4 | |
| 0.0.41 | 4 / 4 | |
| 0.0.40 | 4 / 4 | |
| 0.0.39 | 4 / 4 | |
| 0.0.38 | 4 / 4 | |
| 0.0.37 | 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 | |
| 0.0.27 | 4 / 3 | |
| 0.0.26 | 4 / 3 | |
| 0.0.25 | 4 / 3 | |
| 0.0.24 | 4 / 3 | |
| 0.0.23 | 4 / 3 | |
| 0.0.22 | 4 / 3 | |
| 0.0.21 | 4 / 3 | |
| 0.0.20 | 4 / 3 | |
| 0.0.19 | 4 / 3 | |
| 0.0.18 | 4 / 3 | |
| 0.0.17 | 4 / 3 | |
| 0.0.16 | 4 / 3 | |
| 0.0.15 | 4 / 3 | |
| 0.0.14 | 4 / 3 | |
| 0.0.13 | 4 / 3 |
v0.0.49
2 findingsThis 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.
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 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.