@constructive-io/knative-job-service
knative job service
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are 127.0.0.1 in e2e test files only — not production network calls. | ai | |
| phantom-deps | phantom-dep:@constructive-io/knative-job-fn | AI (phantom-deps): Same-org package; likely re-exported or used indirectly. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@constructive-io/simple-email-fn | AI (phantom-deps): Same-org package; likely re-exported or used indirectly. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@constructive-io/send-email-link-fn | AI (phantom-deps): Same-org package; likely re-exported or used indirectly. Stable false positive for this package. | ai |
Versions (showing 31 of 135)
| Version | Deps | Published |
|---|---|---|
| 0.4.39 | 7 / 1 | |
| 0.4.38 | 7 / 1 | |
| 0.4.37 | 7 / 1 | |
| 0.4.36 | 7 / 1 | |
| 0.4.35 | 7 / 1 | |
| 0.4.34 | 7 / 1 | |
| 0.4.33 | 7 / 1 | |
| 0.4.32 | 7 / 1 | |
| 0.4.31 | 7 / 1 | |
| 0.4.30 | 7 / 1 | |
| 0.4.29 | 7 / 1 | |
| 0.4.28 | 7 / 1 | |
| 0.4.27 | 7 / 1 | |
| 0.4.26 | 7 / 1 | |
| 0.4.25 | 7 / 1 | |
| 0.4.24 | 7 / 1 | |
| 0.4.23 | 7 / 1 | |
| 0.4.22 | 7 / 1 | |
| 0.4.21 | 7 / 1 | |
| 0.4.20 | 7 / 1 | |
| 0.4.19 | 7 / 1 | |
| 0.4.18 | 7 / 1 | |
| 0.4.17 | 7 / 1 | |
| 0.4.16 | 7 / 1 | |
| 0.4.15 | 7 / 1 | |
| 0.4.14 | 7 / 1 | |
| 0.4.13 | 7 / 1 | |
| 0.4.12 | 7 / 1 | |
| 0.4.11 | 7 / 1 | |
| 0.4.10 | 7 / 1 | |
| 0.4.9 | 7 / 1 |
v0.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.