@dbos-inc/koa-serve
DBOS HTTP Package for serving workflows with Koa
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): DBOS framework package; README links to official docs, not a phishing farm. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): jsonwebtoken is a declared runtime dep used indirectly; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/co-body | AI (phantom-deps): Type-only package loaded by framework convention; phantom-dep false positive. | ai | |
| phantom-deps | phantom-dep:serialize-error | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.19.8 | 7 / 10 | |
| 4.18.10 | 7 / 10 | |
| 4.17.6 | 7 / 10 | |
| 4.16.7 | 7 / 10 | |
| 4.15.5 | 7 / 10 | |
| 4.14.6 | 7 / 10 | |
| 4.13.5 | 7 / 10 | |
| 4.12.9 | 7 / 10 | |
| 4.11.11 | 7 / 10 | |
| 4.10.15 | 7 / 10 | |
| 4.9.11 | 7 / 10 | |
| 4.8.8 | 7 / 10 | |
| 4.7.9 | 7 / 10 | |
| 4.6.11 | 7 / 10 | |
| 4.5.13 | 7 / 10 | |
| 4.4.9 | 7 / 10 | |
| 4.2.6 | 7 / 10 | |
| 4.1.6 | 7 / 10 | |
| 4.0.2 | 7 / 10 |
v4.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.