@mesob/auth-hono
Complete Identity and Access Management (IAM) system for Hono applications with type-safe APIs, OpenAPI documentation, and RPC client support.
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by accidentally bundled test files, not injected payload. | ai | |
| source-diff | net-exec-file:dist/lib/turnstile.test.js | AI (source-diff): Bundled vitest test output with standard tsup/esbuild CJS shim; not a dropper. | ai | |
| source-diff | net-exec-file:dist/lib/email-normalize.test.js | AI (source-diff): Bundled vitest test output with standard tsup/esbuild CJS shim; not a dropper. | ai | |
| source-diff | net-exec-file:dist/lib/phone-match.test.js | AI (source-diff): Bundled test file with esbuild boilerplate; not a runtime artifact, no actual network payload. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Early-stage scoped package; metadata gaps are common and not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata signals (no repo, no keywords) are typical for new scoped packages with real ecosystem adoption. | ai | |
| dependencies | unvetted-dep:argon2-wasm-edge | AI (dependencies): argon2-wasm-edge is a declared WASM crypto dep used for password hashing; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:argon2-wasm-edge | AI (phantom-deps): Platform-specific WASM binary; conditional import pattern is expected for this package type. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): JWT library referenced in config/type files; stable false positive for this auth package. | ai | |
| phantom-deps | phantom-dep:hash-wasm | AI (phantom-deps): Platform-specific WASM binary; conditional import pattern is expected for this package type. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.6.17 | 15 / 7 | |
| 0.6.16 | 15 / 7 | |
| 0.6.15 | 15 / 7 | |
| 0.6.14 | 15 / 7 | |
| 0.6.13 | 15 / 7 | |
| 0.6.12 | 15 / 7 | |
| 0.6.11 | 14 / 7 | |
| 0.6.10 | 14 / 7 | |
| 0.6.9 | 14 / 7 | |
| 0.6.8 | 14 / 7 | |
| 0.6.7 | 14 / 7 | |
| 0.6.6 | 14 / 7 | |
| 0.6.5 | 14 / 7 | |
| 0.6.4 | 14 / 7 | |
| 0.6.3 | 14 / 7 | |
| 0.6.2 | 14 / 7 | |
| 0.6.1 | 14 / 7 | |
| 0.6.0 | 14 / 7 | |
| 0.5.11 | 14 / 7 | |
| 0.5.10 | 14 / 7 | |
| 0.5.9 | 14 / 7 | |
| 0.5.8 | 14 / 7 | |
| 0.5.7 | 14 / 7 | |
| 0.5.6 | 14 / 7 | |
| 0.5.5 | 14 / 7 | |
| 0.5.4 | 14 / 7 | |
| 0.5.3 | 14 / 7 | |
| 0.5.2 | 14 / 7 | |
| 0.5.0 | 14 / 7 | |
| 0.4.7 | 14 / 7 | |
| 0.4.6 | 14 / 7 | |
| 0.4.5 | 14 / 7 | |
| 0.4.4 | 14 / 7 | |
| 0.4.3 | 14 / 7 | |
| 0.4.2 | 14 / 7 | |
| 0.4.1 | 14 / 7 | |
| 0.4.0 | 14 / 7 | |
| 0.3.5 | 14 / 7 | |
| 0.3.4 | 14 / 7 | |
| 0.3.3 | 14 / 7 | |
| 0.3.2 | 14 / 7 | |
| 0.3.1 | 14 / 7 | |
| 0.3.0 | 14 / 7 | |
| 0.2.5 | 14 / 7 | |
| 0.2.4 | 14 / 7 | |
| 0.2.3 | 14 / 7 | |
| 0.2.2 | 14 / 7 | |
| 0.2.1 | 14 / 7 | |
| 0.2.0 | 14 / 7 | |
| 0.1.1 | 14 / 7 | |
| 0.1.0 | 14 / 7 |
v0.6.17
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.