@enkaku/server
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Small monorepo sub-package, sparse metadata is expected pattern. | ai | |
| dependencies | unvetted-dep:@enkaku/jwt | AI (dependencies): Sibling package in same monorepo, pinned to matching version. | ai | |
| dependencies | unvetted-dep:@enkaku/util | AI (dependencies): Sibling package in same monorepo, version-locked; not an external unvetted dep. | ai | |
| dependencies | unvetted-dep:@kokuin/token | AI (dependencies): Consistent internal scope dep, no malicious signal. | ai | |
| dependencies | unvetted-dep:@kokuin/capability | AI (dependencies): Consistent internal scope dep, no malicious signal. | ai | |
| dependencies | unvetted-dep:@sozai/log | AI (dependencies): Consistent internal scope dep used across this maintainer's monorepo family, no malicious signal. | ai | |
| dependencies | unvetted-dep:@sozai/otel | AI (dependencies): Consistent internal scope dep, no malicious signal. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @enkaku/* monorepo package; edit-distance match to 'semver' is coincidental, not a typosquat. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 11 / 1 | |
| 0.18.1 | 11 / 1 | |
| 0.18.0 | 10 / 1 | |
| 0.17.1 | 10 / 1 | |
| 0.17.0 | 10 / 1 | |
| 0.16.0 | 10 / 1 | |
| 0.15.1 | 10 / 1 | |
| 0.15.0 | 10 / 1 | |
| 0.14.4 | 10 / 1 | |
| 0.14.3 | 10 / 1 | |
| 0.14.2 | 9 / 1 | |
| 0.14.1 | 9 / 1 | |
| 0.14.0 | 9 / 1 | |
| 0.13.3 | 8 / 1 | |
| 0.13.2 | 8 / 1 | |
| 0.13.1 | 8 / 1 | |
| 0.13.0 | 8 / 1 | |
| 0.12.3 | 8 / 1 | |
| 0.12.2 | 8 / 1 | |
| 0.12.1 | 7 / 1 | |
| 0.12.0 | 7 / 1 | |
| 0.11.0 | 7 / 1 | |
| 0.10.0 | 7 / 1 | |
| 0.9.1 | 6 / 1 | |
| 0.8.1 | 6 / 1 | |
| 0.8.0 | 6 / 1 | |
| 0.5.0 | 4 / 2 | |
| 0.3.1 | 4 / 2 | |
| 0.3.0 | 4 / 2 |
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
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.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.