@kubbisec/naus
KubbiSec Naus CI/CD Runner — install globally, run anywhere
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI runner tool; child_process is expected for spawning pipeline/CI processes. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 1.0.79 | 0 / 0 | |
| 1.0.78 | 0 / 0 | |
| 1.0.77 | 0 / 0 | |
| 1.0.76 | 0 / 0 | |
| 1.0.75 | 0 / 0 | |
| 1.0.74 | 0 / 0 | |
| 1.0.73 | 0 / 0 | |
| 1.0.72 | 0 / 0 | |
| 1.0.71 | 0 / 0 | |
| 1.0.70 | 0 / 0 | |
| 1.0.69 | 0 / 0 | |
| 1.0.68 | 0 / 0 | |
| 1.0.67 | 4 / 0 | |
| 1.0.66 | 0 / 0 | |
| 1.0.65 | 0 / 0 | |
| 1.0.64 | 0 / 0 | |
| 1.0.63 | 0 / 0 | |
| 1.0.59 | 0 / 0 | |
| 1.0.58 | 0 / 0 | |
| 1.0.57 | 0 / 0 | |
| 1.0.56 | 0 / 0 | |
| 1.0.55 | 0 / 0 | |
| 1.0.54 | 0 / 0 | |
| 1.0.53 | 0 / 0 | |
| 1.0.52 | 0 / 0 | |
| 1.0.51 | 0 / 0 | |
| 1.0.50 | 0 / 0 | |
| 1.0.49 | 0 / 0 | |
| 1.0.48 | 0 / 0 | |
| 1.0.47 | 0 / 0 | |
| 1.0.46 | 0 / 0 | |
| 1.0.45 | 0 / 0 | |
| 1.0.44 | 0 / 0 | |
| 1.0.43 | 0 / 0 | |
| 1.0.42 | 0 / 0 | |
| 1.0.41 | 0 / 0 | |
| 1.0.40 | 0 / 0 | |
| 1.0.39 | 0 / 0 | |
| 1.0.38 | 0 / 0 | |
| 1.0.37 | 0 / 0 | |
| 1.0.36 | 0 / 0 | |
| 1.0.35 | 0 / 0 | |
| 1.0.34 | 0 / 0 | |
| 1.0.33 | 0 / 0 | |
| 1.0.32 | 0 / 0 | |
| 1.0.31 | 0 / 0 | |
| 1.0.30 | 0 / 0 | |
| 1.0.29 | 0 / 0 | |
| 1.0.28 | 0 / 0 | |
| 1.0.27 | 0 / 0 | |
| 1.0.26 | 0 / 0 |
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.