@imolko/ultra-reporter
Reporter and documentation for: domain, use-cases and tests
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:env-spread | AI (semgrep): Spreading process.env into child_process exec options is standard practice for passing env context to subprocesses; not exfiltration. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Build/reporter tool legitimately uses child_process to run commands; expected pattern for this package type. | ai | |
| phantom-deps | phantom-dep:jsdoc | AI (phantom-deps): Referenced in config files only; stable false positive for this documentation tooling package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:better-docs | AI (phantom-deps): Referenced in config files only; stable false positive for this documentation tooling package. | ai | |
| phantom-deps | phantom-dep:jest-html-reporters | AI (phantom-deps): Referenced in config files only; stable false positive for this reporter package. | ai | |
| phantom-deps | phantom-dep:@imolko/ultra-tsconfig | AI (phantom-deps): Same org scope, referenced in config files; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.1.22 | 10 / 9 | |
| 2.1.21 | 10 / 9 | |
| 2.1.19 | 10 / 9 | |
| 2.1.16 | 10 / 9 |
v2.1.22
2 findingsSpreading entire process.env into an object — may capture all secrets 18 | const childProcess = (0, child_process_1.exec)(command, { 19 | // Establecer variables de entorno para scripts internos > 20 | env: { 21 | ...process.env, 22 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.16
2 findingsSpreading entire process.env into an object — may capture all secrets 18 | const childProcess = (0, child_process_1.exec)(command, { 19 | // Establecer variables de entorno para scripts internos > 20 | env: { 21 | ...process.env, 22 | },
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.