@qelos/api-kit
API-Kit package to help with qelos infrastructure and reuse capabilities across services
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Require of a temp file in shutdown logic; not arbitrary user-controlled input. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode of an HTTP header for backward-compatible user JSON parsing; no payload execution. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 4 / 3 | |
| 4.1.1 | 4 / 3 | |
| 4.1.0 | 4 / 3 | |
| 4.0.0 | 4 / 3 | |
| 3.11.11 | 4 / 2 | |
| 3.11.10 | 4 / 2 | |
| 3.11.9 | 4 / 2 | |
| 3.11.8 | 4 / 2 | |
| 3.11.7 | 4 / 2 | |
| 3.11.6 | 4 / 2 | |
| 3.11.5 | 4 / 2 | |
| 3.11.4 | 4 / 2 | |
| 3.11.3 | 4 / 2 | |
| 3.11.2 | 4 / 2 | |
| 3.11.1 | 4 / 2 | |
| 3.11.0 | 4 / 2 | |
| 3.10.0 | 4 / 2 | |
| 3.9.0 | 4 / 2 | |
| 3.8.3 | 4 / 2 | |
| 3.8.2 | 4 / 2 | |
| 3.8.1 | 4 / 2 | |
| 3.8.0 | 4 / 2 | |
| 3.7.7 | 4 / 2 | |
| 3.7.4 | 4 / 2 | |
| 3.7.3 | 4 / 2 | |
| 3.7.2 | 4 / 2 | |
| 3.7.1 | 4 / 2 | |
| 3.7.0 | 4 / 2 | |
| 3.6.6 | 4 / 2 | |
| 3.6.2 | 4 / 2 | |
| 3.6.1 | 4 / 2 | |
| 3.6.0 | 4 / 2 | |
| 3.5.5 | 4 / 2 | |
| 3.5.4 | 4 / 2 | |
| 3.4.1 | 4 / 2 | |
| 3.4.0 | 4 / 2 | |
| 3.3.9 | 4 / 2 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.