@privateaim/server-kit
This package contains common constants, functions, types, ... for the server side.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): triple-beam and winston-transport are established Winston logging packages; addition is consistent with adding logging support. | ai | |
| phantom-deps | phantom-dep:hapic | AI (phantom-deps): hapic is a declared runtime dep; phantom-dep heuristic fires due to indirect/config-only usage, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ebec/http | AI (phantom-deps): Declared runtime dep; phantom-dep fires due to config-only reference, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:triple-beam | AI (phantom-deps): Declared runtime dep used transitively via winston; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 11 / 8 | |
| 0.10.0 | 11 / 8 | |
| 0.8.43 | 12 / 8 | |
| 0.8.42 | 12 / 8 | |
| 0.8.41 | 12 / 8 | |
| 0.8.39 | 12 / 8 | |
| 0.8.38 | 12 / 8 | |
| 0.8.37 | 12 / 5 | |
| 0.8.36 | 12 / 5 | |
| 0.8.34 | 13 / 5 | |
| 0.8.33 | 13 / 5 | |
| 0.8.32 | 13 / 5 | |
| 0.8.31 | 11 / 5 | |
| 0.8.30 | 11 / 5 | |
| 0.8.29 | 11 / 5 | |
| 0.8.28 | 10 / 6 | |
| 0.8.27 | 10 / 6 | |
| 0.8.26 | 10 / 6 | |
| 0.8.25 | 10 / 6 | |
| 0.8.23 | 10 / 6 | |
| 0.8.22 | 10 / 6 | |
| 0.8.21 | 10 / 5 | |
| 0.8.20 | 10 / 5 | |
| 0.8.19 | 10 / 5 | |
| 0.8.18 | 10 / 5 | |
| 0.8.17 | 10 / 5 | |
| 0.8.16 | 9 / 5 | |
| 0.8.15 | 11 / 5 | |
| 0.8.14 | 9 / 5 | |
| 0.8.13 | 8 / 5 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.