← Home

@frontegg/vue

npm
51
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

front-eggguy_fronteggraz.shlomo.fe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Established org package; empty description is cosmetic, not a risk signal. ai
bogus-package bogus-package AI (bogus-package): Scoped org package (@frontegg) with 542 versions; missing metadata is a style choice, not a spam indicator. ai
typosquat typosquat.levenshtein:vite AI (typosquat): Scoped @frontegg/vue is a legitimate Vue SDK; Levenshtein match to 'vite' is a false positive. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped @frontegg/vue is a legitimate Vue SDK; Levenshtein match to 'yup' is a false positive. ai

Versions (showing 51 of 70)

View all versions
Version Deps Published
4.12.0 3 / 27
4.11.9 3 / 27
4.11.8 3 / 27
4.11.7 3 / 27
4.11.6 3 / 27
4.11.5 3 / 27
4.11.4 3 / 27
4.11.3 3 / 27
4.11.2 3 / 27
4.11.1 3 / 27
4.11.0 3 / 27
4.10.17 3 / 27
4.10.16 3 / 27
4.10.15 3 / 27
4.10.14 3 / 27
4.10.13 3 / 27
4.10.12 3 / 27
4.10.11 3 / 27
4.10.10 3 / 27
4.10.9 3 / 27
4.10.8 3 / 27
4.10.7 3 / 27
4.10.6 3 / 27
4.10.5 3 / 27
4.10.4 3 / 27
4.10.3 3 / 27
4.10.2 3 / 27
4.10.1 3 / 27
4.10.0 3 / 27
4.9.1 3 / 27
4.9.0 3 / 27
4.8.0 3 / 27
4.7.2 3 / 27
4.7.1 3 / 27
4.7.0 3 / 27
4.6.5 3 / 27
4.6.4 3 / 27
4.6.3 3 / 27
4.6.2 3 / 27
4.6.1 3 / 27
4.6.0 3 / 27
4.5.1 3 / 27
4.5.0 3 / 27
4.4.9 3 / 27
4.4.8 3 / 27
4.4.7 3 / 27
4.4.6 3 / 27
4.4.5 3 / 27
4.4.4 3 / 27
4.4.3 3 / 27
4.4.2 3 / 27

v4.12.0

1 finding
LOW No provenance attestation provenance

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

v4.11.9

1 finding
LOW No provenance attestation provenance

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

v4.11.8

1 finding
LOW No provenance attestation provenance

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

v4.11.7

1 finding
LOW No provenance attestation provenance

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

v4.7.0

1 finding
LOW No provenance attestation provenance

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

v4.6.5

1 finding
LOW No provenance attestation provenance

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

v4.6.4

1 finding
LOW No provenance attestation provenance

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

v4.6.3

1 finding
LOW No provenance attestation provenance

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

v4.6.2

1 finding
LOW No provenance attestation provenance

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

v4.6.1

1 finding
LOW No provenance attestation provenance

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

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

v4.5.1

1 finding
LOW No provenance attestation provenance

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

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.4.9

1 finding
LOW No provenance attestation provenance

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

v4.4.8

1 finding
LOW No provenance attestation provenance

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

v4.4.7

1 finding
LOW No provenance attestation provenance

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

v4.4.6

1 finding
LOW No provenance attestation provenance

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

v4.4.5

1 finding
LOW No provenance attestation provenance

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

v4.4.4

1 finding
LOW No provenance attestation provenance

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

v4.4.3

1 finding
LOW No provenance attestation provenance

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

v4.4.2

1 finding
LOW No provenance attestation provenance

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