@cordisjs/plugin-server
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/koa | AI (phantom-deps): TypeScript type package for the koa framework; framework-scoped, loaded by convention. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/koa__router | AI (phantom-deps): TypeScript type package for @koa/router; framework-scoped, loaded by convention. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:reggol | AI (phantom-deps): reggol is a logging library in the Cordis ecosystem; referenced in config files as documented. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): @types/ws is intentionally listed as a runtime dep in this package to expose WebSocket types to consumers; stable pattern for this plugin. | ai | |
| phantom-deps | phantom-dep:path-to-regexp | AI (phantom-deps): path-to-regexp is a routing utility used indirectly/via config in this server plugin; phantom-dep flag is a stable false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 8 / 3 | |
| 1.6.2 | 7 / 3 | |
| 1.6.1 | 7 / 3 | |
| 1.6.0 | 7 / 5 | |
| 1.5.0 | 7 / 5 | |
| 1.4.0 | 7 / 5 | |
| 1.3.0 | 7 / 5 | |
| 1.2.0 | 5 / 2 | |
| 1.1.1 | 5 / 2 | |
| 1.1.0 | 5 / 2 | |
| 1.0.4 | 5 / 2 | |
| 1.0.3 | 5 / 2 | |
| 1.0.2 | 5 / 2 | |
| 1.0.1 | 5 / 2 | |
| 1.0.0 | 5 / 2 | |
| 0.2.9 | 12 / 1 | |
| 0.2.8 | 12 / 1 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.