@imolko/ultra-ddd-essentials
Artefactos básicos
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in a formula/condition executor for dynamic expression evaluation; consistent with the package's DDD essentials purpose. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ajv-formats | AI (phantom-deps): ajv-formats is a declared dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@imolko/ultra-tsconfig | AI (phantom-deps): Same-org tsconfig package; used as a build dependency, not directly imported in source. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 4 / 7 | |
| 2.0.1 | 3 / 6 | |
| 2.0.0 | 3 / 6 | |
| 1.1.30 | 4 / 6 | |
| 1.1.28 | 4 / 6 | |
| 1.1.25 | 0 / 6 | |
| 1.1.23 | 0 / 6 | |
| 1.1.22 | 0 / 6 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.