@nx-ddd/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 NX/Angular DDD library; name similarity to 'cors' is coincidental, not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript runtime dep; phantom-dep false positive for compiled Angular libraries. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 19.51.0 | 1 / 0 | |
| 19.50.0 | 1 / 0 | |
| 19.49.0 | 1 / 0 | |
| 19.48.0 | 1 / 0 | |
| 19.47.0 | 1 / 0 | |
| 19.46.1 | 1 / 0 | |
| 19.46.0 | 1 / 0 | |
| 19.45.2 | 1 / 0 | |
| 19.45.1 | 1 / 0 | |
| 19.45.0 | 1 / 0 | |
| 19.44.0 | 1 / 0 | |
| 19.43.0 | 1 / 0 | |
| 19.42.0 | 1 / 0 | |
| 19.39.0 | 1 / 0 | |
| 19.38.1 | 1 / 0 | |
| 19.38.0 | 1 / 0 | |
| 19.37.0 | 1 / 0 | |
| 19.36.0 | 1 / 0 | |
| 19.35.0 | 1 / 0 | |
| 19.34.0 | 1 / 0 | |
| 19.33.1 | 1 / 0 | |
| 19.33.0 | 1 / 0 | |
| 19.32.0 | 1 / 0 | |
| 19.31.0 | 1 / 0 | |
| 19.30.0 | 1 / 0 | |
| 19.29.0 | 1 / 0 | |
| 19.28.0 | 1 / 0 | |
| 19.27.0 | 1 / 0 | |
| 19.26.0 | 1 / 0 | |
| 19.25.0 | 1 / 0 | |
| 19.24.1 | 1 / 0 | |
| 19.21.8 | 1 / 0 | |
| 19.21.7 | 1 / 0 | |
| 19.21.6 | 1 / 0 | |
| 19.21.5 | 1 / 0 | |
| 19.21.3 | 1 / 0 | |
| 19.21.2 | 1 / 0 | |
| 19.21.1 | 1 / 0 | |
| 19.21.0 | 1 / 0 | |
| 19.20.0 | 1 / 0 | |
| 19.19.1 | 1 / 0 | |
| 19.19.0 | 1 / 0 | |
| 19.18.0 | 1 / 0 | |
| 19.17.0 | 1 / 0 | |
| 19.16.0 | 1 / 0 | |
| 19.15.0 | 1 / 0 | |
| 19.14.0 | 1 / 0 | |
| 19.13.1 | 1 / 0 | |
| 19.13.0 | 1 / 0 | |
| 19.12.6 | 1 / 0 | |
| 19.12.5 | 1 / 0 |
v19.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.49.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.48.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.47.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.46.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.46.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.45.2
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.45.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.45.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.44.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.43.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.42.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.39.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.38.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.38.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.37.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.36.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.35.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.34.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.33.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.33.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.32.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.31.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.30.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.29.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.28.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.27.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.26.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.25.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.24.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.8
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.7
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.6
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.5
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.3
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.2
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.21.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.20.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.19.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.19.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.18.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.17.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.16.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.15.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.14.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.13.1
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.13.0
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.12.6
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.12.5
2 findingsPackage name '@nx-ddd/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.