@ddd-ts/types
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Types-only monorepo package; empty dist/index.js and missing description are structural, not malicious. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across 271 versions of this monorepo package; not a spam indicator here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.0.49 | 0 / 1 | |
| 0.0.48 | 0 / 1 | |
| 0.0.47 | 0 / 1 | |
| 0.0.46 | 0 / 1 | |
| 0.0.45 | 0 / 1 | |
| 0.0.44 | 0 / 1 | |
| 0.0.42 | 0 / 1 | |
| 0.0.40 | 0 / 1 | |
| 0.0.39 | 0 / 1 | |
| 0.0.38 | 0 / 1 | |
| 0.0.37 | 0 / 1 | |
| 0.0.36 | 0 / 1 | |
| 0.0.35 | 0 / 1 | |
| 0.0.34 | 0 / 1 | |
| 0.0.33 | 0 / 1 | |
| 0.0.32 | 0 / 1 | |
| 0.0.31 | 0 / 1 | |
| 0.0.30 | 0 / 1 | |
| 0.0.29 | 0 / 1 | |
| 0.0.28 | 0 / 1 | |
| 0.0.27 | 0 / 1 | |
| 0.0.26 | 0 / 1 | |
| 0.0.25 | 0 / 1 | |
| 0.0.24 | 0 / 1 | |
| 0.0.23 | 0 / 1 | |
| 0.0.22 | 0 / 1 | |
| 0.0.21 | 0 / 1 | |
| 0.0.20 | 0 / 1 | |
| 0.0.19 | 0 / 1 | |
| 0.0.18 | 0 / 1 | |
| 0.0.17 | 0 / 1 | |
| 0.0.16 | 0 / 1 | |
| 0.0.15 | 0 / 1 | |
| 0.0.14 | 0 / 1 | |
| 0.0.13 | 0 / 1 | |
| 0.0.12 | 0 / 1 | |
| 0.0.11 | 0 / 1 | |
| 0.0.10 | 0 / 1 | |
| 0.0.9 | 0 / 1 |
v0.0.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.48
1 findingPublished 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.