@feathersjs/authentication
Add Authentication to your FeathersJS app.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:long-timeout | AI (dependencies): long-timeout is a well-known, stable utility package; its use in @feathersjs/authentication is legitimate and consistent across versions. | ai | |
| dependencies | unvetted-dep:@feathersjs/hooks | AI (dependencies): First-party @feathersjs monorepo package; legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@feathersjs/schema | AI (dependencies): First-party @feathersjs monorepo package; legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@feathersjs/feathers | AI (dependencies): First-party @feathersjs monorepo package; core framework dependency, always expected here. | ai | |
| dependencies | unvetted-dep:@feathersjs/transport-commons | AI (dependencies): First-party @feathersjs monorepo package; legitimate dependency for this package. | ai | |
| phantom-deps | phantom-dep:@types/jsonwebtoken | AI (phantom-deps): @types/jsonwebtoken is intentionally listed as a runtime dep to expose JWT type declarations to TypeScript consumers; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package (3103 days old, 142 versions) published before provenance was common; absence is not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.0.44 | 11 / 9 | |
| 5.0.43 | 11 / 9 | |
| 5.0.42 | 11 / 9 | |
| 5.0.41 | 11 / 9 | |
| 5.0.40 | 11 / 9 | |
| 5.0.39 | 11 / 9 | |
| 5.0.37 | 11 / 9 | |
| 5.0.36 | 11 / 9 | |
| 5.0.35 | 11 / 9 | |
| 5.0.34 | 11 / 9 | |
| 4.5.19 | 9 / 10 |
v5.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.