@imolko/ultra-generator
Generador para proyectos relacionados con @imolko/ultra-ddd
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:dynamic-require | AI (semgrep): Resolves internal resource paths via a helper function, not user-controlled input; stable CLI pattern for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): CLI generator tool legitimately passes process.env to child processes for nx/nrwl command execution. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process use is expected in a CLI code generator that invokes build/nx commands. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.1.16 | 5 / 9 | |
| 2.1.15 | 5 / 9 | |
| 2.1.14 | 5 / 9 | |
| 2.1.13 | 5 / 9 | |
| 2.1.12 | 5 / 9 | |
| 2.1.11 | 5 / 9 | |
| 2.1.9 | 5 / 9 | |
| 2.1.8 | 5 / 9 | |
| 2.1.7 | 5 / 9 | |
| 2.1.6 | 5 / 9 | |
| 2.1.3 | 6 / 8 | |
| 2.0.0 | 7 / 7 | |
| 1.0.21 | 7 / 7 | |
| 1.0.20 | 6 / 7 |
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
2 findingsSpreading entire process.env into an object — may capture all secrets 9 | { 10 | // Establecer variables de entorno para scripts internos > 11 | env: { 12 | ...process.env, 13 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
2 findingsSpreading entire process.env into an object — may capture all secrets 9 | { 10 | // Establecer variables de entorno para scripts internos > 11 | env: { 12 | ...process.env, 13 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
2 findingsSpreading entire process.env into an object — may capture all secrets 9 | { 10 | // Establecer variables de entorno para scripts internos > 11 | env: { 12 | ...process.env, 13 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
2 findingsSpreading entire process.env into an object — may capture all secrets 9 | { 10 | // Establecer variables de entorno para scripts internos > 11 | env: { 12 | ...process.env, 13 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
2 findingsSpreading entire process.env into an object — may capture all secrets 9 | { 10 | // Establecer variables de entorno para scripts internos > 11 | env: { 12 | ...process.env, 13 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.