← Home

@adminforth/oauth

npm Repository Homepage

AdminForth OAuth Plugin

43
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

vanbroshdominic-de-cocovitasikaakopyan12345noone7135yaroslav8765

Keywords

adminforthoauthgoogle authgithub auth

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Decoding OAuth state parameter is standard practice; not a malicious payload pattern for this package. ai

Versions (showing 43 of 43)

Version Deps Published
1.10.1 1 / 5
1.10.0 1 / 5
1.9.3 0 / 5
1.9.2 0 / 5
1.9.1 0 / 5
1.9.0 0 / 5
1.8.0 0 / 5
1.7.8 0 / 5
1.7.7 0 / 5
1.7.6 0 / 5
1.7.5 0 / 5
1.7.4 0 / 5
1.7.3 0 / 5
1.7.2 0 / 5
1.7.1 0 / 5
1.7.0 0 / 5
1.6.14 0 / 5
1.6.12 0 / 5
1.6.11 0 / 5
1.6.10 0 / 5
1.6.9 0 / 5
1.6.8 0 / 4
1.6.6 0 / 4
1.6.5 0 / 4
1.6.4 0 / 4
1.6.3 0 / 4
1.6.2 0 / 4
1.6.1 0 / 4
1.6.0 0 / 4
1.5.0 0 / 4
1.4.3 1 / 4
1.4.2 1 / 4
1.4.1 1 / 4
1.4.0 1 / 4
1.3.2 1 / 4
1.3.1 0 / 4
1.3.0 0 / 4
1.2.0 0 / 4
1.1.2 0 / 4
1.1.1 0 / 4
1.1.0 0 / 4
1.0.2 0 / 4
1.0.1 0 / 4

v1.10.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

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.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.