@privateaim/server-core-worker-kit
[![npm version][npm-src]][npm-href]
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package pattern; missing description is consistent across the @privateaim family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo sub-package; missing metadata is expected for this package family. | ai | |
| phantom-deps | phantom-dep:singa | AI (phantom-deps): singa is a declared runtime dependency; phantom-dep heuristic fires but it is legitimately referenced. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is common and not a risk indicator here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 3 / 1 | |
| 0.10.0 | 3 / 1 | |
| 0.7.46 | 3 / 1 | |
| 0.7.44 | 3 / 1 | |
| 0.7.43 | 3 / 1 | |
| 0.7.42 | 3 / 1 | |
| 0.7.40 | 3 / 1 | |
| 0.7.39 | 3 / 1 | |
| 0.7.38 | 3 / 1 | |
| 0.7.37 | 3 / 1 | |
| 0.7.35 | 4 / 1 | |
| 0.7.34 | 4 / 1 | |
| 0.7.33 | 4 / 1 | |
| 0.7.32 | 4 / 1 | |
| 0.7.31 | 4 / 1 | |
| 0.7.30 | 4 / 1 | |
| 0.7.29 | 4 / 1 | |
| 0.7.28 | 4 / 1 | |
| 0.7.27 | 4 / 1 | |
| 0.7.26 | 4 / 1 | |
| 0.7.24 | 4 / 1 | |
| 0.7.23 | 4 / 1 | |
| 0.7.22 | 4 / 1 | |
| 0.7.21 | 4 / 1 | |
| 0.7.20 | 4 / 1 | |
| 0.7.19 | 4 / 1 | |
| 0.7.18 | 4 / 1 | |
| 0.7.17 | 4 / 1 |
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.