@adminforth/two-factors-auth
AdminForth plugin for two factors authentication
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-2fa | AI (dependencies): node-2fa is the canonical TOTP library for Node.js; expected dependency for a 2FA plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established adminforth plugin org; provenance absence is common and not a risk signal here. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 3 / 5 | |
| 4.3.4 | 3 / 5 | |
| 4.3.3 | 3 / 5 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 5 | |
| 4.3.0 | 3 / 5 | |
| 4.2.4 | 2 / 5 | |
| 4.2.3 | 2 / 5 | |
| 4.2.2 | 2 / 5 | |
| 4.2.1 | 2 / 5 | |
| 4.2.0 | 2 / 5 | |
| 4.1.5 | 2 / 5 | |
| 4.1.4 | 2 / 5 | |
| 4.1.3 | 2 / 5 | |
| 4.1.2 | 2 / 5 | |
| 4.1.1 | 2 / 5 | |
| 4.1.0 | 2 / 5 | |
| 4.0.2 | 2 / 5 | |
| 4.0.1 | 2 / 5 | |
| 4.0.0 | 2 / 5 | |
| 3.3.10 | 2 / 5 | |
| 3.3.9 | 2 / 5 | |
| 3.3.8 | 2 / 5 | |
| 3.3.7 | 2 / 5 | |
| 3.3.6 | 2 / 5 | |
| 3.3.5 | 2 / 5 | |
| 3.3.4 | 2 / 5 | |
| 3.3.3 | 2 / 5 | |
| 3.3.2 | 2 / 5 | |
| 3.3.1 | 2 / 5 | |
| 3.3.0 | 2 / 5 | |
| 3.2.3 | 2 / 5 | |
| 3.2.2 | 2 / 5 | |
| 3.2.1 | 2 / 5 | |
| 3.2.0 | 2 / 4 | |
| 3.1.5 | 2 / 4 | |
| 3.1.4 | 2 / 4 | |
| 3.1.3 | 2 / 4 | |
| 3.1.2 | 2 / 4 | |
| 3.1.1 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.5 | 2 / 4 | |
| 3.0.4 | 2 / 4 | |
| 3.0.3 | 2 / 4 | |
| 3.0.2 | 2 / 4 | |
| 3.0.1 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.10.12 | 2 / 4 | |
| 2.10.11 | 2 / 4 | |
| 2.10.10 | 2 / 4 | |
| 2.10.9 | 2 / 4 |
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.