← Home

@oakbun/jwt

npm Repository Homepage

JWT plugin for the OakBun framework.

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

codingruo

Keywords

bunjwttypescriptbackendoakbun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped JWT plugin for OakBun framework; not a typo of jest. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped JWT plugin for OakBun framework; not a typo of got. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped JWT plugin for OakBun framework; not a typo of joi. ai

Versions (showing 7 of 7)

Version Deps Published
4.0.1 1 / 1
4.0.0 1 / 1
3.0.0 1 / 1
2.0.0 1 / 1
1.0.0 1 / 1
0.1.1 1 / 1
0.1.0 1 / 1

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.