@kth/api-call
Node.js module to make JSON calls against APIs.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): KTH org maintainer reshuffle, publisher has long clean track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal org maintainer turnover, no takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic internal utility package; dormancy expected, no material code changes. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 4.5.2 | 3 / 12 | |
| 4.5.1 | 3 / 12 | |
| 4.5.0 | 3 / 12 | |
| 4.4.0 | 4 / 11 | |
| 4.3.1 | 4 / 11 | |
| 4.3.0 | 4 / 11 | |
| 4.2.1 | 4 / 13 | |
| 4.2.0 | 4 / 13 | |
| 4.1.0 | 4 / 13 | |
| 4.0.40 | 4 / 13 | |
| 4.0.39 | 4 / 13 | |
| 4.0.38 | 4 / 13 | |
| 4.0.37 | 4 / 13 | |
| 4.0.36 | 4 / 13 | |
| 4.0.35 | 4 / 13 | |
| 4.0.34 | 4 / 13 | |
| 4.0.33 | 4 / 13 | |
| 4.0.32 | 4 / 13 | |
| 4.0.31 | 4 / 13 | |
| 4.0.30 | 4 / 13 | |
| 4.0.29 | 4 / 13 | |
| 4.0.28 | 4 / 13 | |
| 4.0.27 | 4 / 13 | |
| 4.0.26 | 4 / 13 | |
| 4.0.25 | 4 / 13 | |
| 4.0.24 | 4 / 13 | |
| 4.0.23 | 4 / 13 | |
| 4.0.22 | 4 / 13 | |
| 4.0.21 | 5 / 13 | |
| 4.0.20 | 5 / 13 | |
| 4.0.19 | 5 / 13 | |
| 4.0.18 | 5 / 13 | |
| 4.0.17 | 5 / 13 | |
| 4.0.16 | 5 / 13 | |
| 4.0.15 | 5 / 13 | |
| 4.0.14 | 5 / 13 | |
| 4.0.13 | 5 / 13 | |
| 4.0.12 | 5 / 13 | |
| 4.0.11 | 5 / 12 | |
| 4.0.10 | 4 / 11 | |
| 4.0.9 | 4 / 11 | |
| 4.0.8 | 4 / 14 | |
| 4.0.7 | 4 / 15 | |
| 4.0.6 | 4 / 15 | |
| 4.0.5 | 4 / 15 | |
| 4.0.4 | 4 / 15 | |
| 4.0.3 | 4 / 15 | |
| 4.0.2 | 4 / 15 | |
| 4.0.1 | 4 / 15 | |
| 4.0.0 | 4 / 15 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.