joey
A Sinatra-like web server configuration language for JavaScript, built on Q, Q-IO, and JSGI.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): joey is a long-established JSGI/Q web framework by kriskowal, completely unrelated to joi (validation library). Name similarity is purely coincidental. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from montage-bot to kriskowal occurred in 2013 — over 11 years ago. kriskowal is the canonical maintainer of this package with a strong trust record. This is a stable historical fact, not a risk. | ai | |
| phantom-deps | phantom-dep:url2 | AI (phantom-deps): url2 is a declared runtime dependency; phantom-dep finding reflects indirect usage pattern, not a security issue for this package. | ai | |
| phantom-deps | phantom-dep:optimist | AI (phantom-deps): optimist is a declared runtime dependency; phantom-dep finding reflects indirect usage pattern, not a security issue for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 1 | |
| 2.0.0 | 4 / 1 | |
| 1.5.3 | 4 / 1 | |
| 1.5.2 | 4 / 1 | |
| 1.5.1 | 4 / 1 | |
| 1.5.0 | 4 / 1 | |
| 1.4.0 | 4 / 1 | |
| 1.3.3 | 4 / 1 | |
| 1.3.2 | 4 / 1 | |
| 1.3.1 | 4 / 1 | |
| 1.3.0 | 4 / 1 | |
| 1.2.1 | 4 / 1 | |
| 1.2.0 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 | |
| 1.0.0 | 4 / 1 | |
| 0.1.3 | 4 / 1 | |
| 0.1.2 | 4 / 1 | |
| 0.1.1 | 4 / 1 | |
| 0.1.0 | 4 / 1 | |
| 0.0.15 | 5 / 1 | |
| 0.0.14 | 4 / 1 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
2 findingsMaintainer email '[email protected]' uses domain 'montagestudio.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2013-06-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2013-06-04. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.