@frontegg/js No license 43 versions

@frontegg/js

npm

43

Versions

—

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

front-eggguy_fronteggraz.shlomo.fe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped @frontegg/js is a legitimate SDK package; short-suffix Levenshtein match against 'qs' is a stable false positive.	ai	2026/05/03
typosquat	typosquat.levenshtein:jest	AI (typosquat): Same scoped-package false positive pattern; not a typosquat of jest.	ai	2026/05/03
typosquat	typosquat.levenshtein:pg	AI (typosquat): Same scoped-package false positive pattern; not a typosquat of pg.	ai	2026/05/03
typosquat	typosquat.levenshtein:rxjs	AI (typosquat): Same scoped-package false positive pattern; not a typosquat of rxjs.	ai	2026/05/03
typosquat	typosquat.levenshtein:joi	AI (typosquat): Same scoped-package false positive pattern; not a typosquat of joi.	ai	2026/05/03
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Same scoped-package false positive pattern; not a typosquat of ajv.	ai	2026/05/03

Versions (showing 43 of 43)

Version	Deps	Published
7.110.0	2 / 0	2026-06-04
7.109.0	2 / 0	2026-05-31
7.108.0	2 / 0	2026-05-19
7.107.0	2 / 0	2026-05-17
7.106.0	2 / 0	2026-05-05
7.105.0	2 / 0	2026-05-03
7.104.0	2 / 0	2026-03-31
7.103.0	2 / 0	2026-03-19
7.102.0	2 / 0	2026-03-08
7.101.0	2 / 0	2026-02-16
7.100.0	2 / 0	2026-02-10
7.99.0	2 / 0	2026-01-27
7.98.0	2 / 0	2026-01-26
7.97.0	2 / 0	2026-01-14
7.96.0	2 / 0	2026-01-05
7.95.0	2 / 0	2025-12-11
7.94.0	2 / 0	2025-12-07
7.93.0	2 / 0	2025-11-30
7.92.0	2 / 0	2025-10-19
7.91.0	2 / 0	2025-09-29
7.90.0	2 / 0	2025-09-25
7.89.0	2 / 0	2025-09-16
7.88.0	2 / 0	2025-09-15
7.87.0	2 / 0	2025-09-14
7.86.0	2 / 0	2025-09-10
7.85.0	2 / 0	2025-09-04
7.84.0	2 / 0	2025-09-03
7.83.0	2 / 0	2025-09-01
7.82.0	2 / 0	2025-08-12
7.81.0	2 / 0	2025-07-29
7.80.0	2 / 0	2025-07-06
7.79.0	2 / 0	2025-06-24
7.78.0	2 / 0	2025-06-23
7.77.0	2 / 0	2025-06-16
7.76.0	2 / 0	2025-06-12
7.75.0	2 / 0	2025-06-07
7.74.0	2 / 0	2025-05-27
7.73.0	2 / 0	2025-05-21
7.72.0	2 / 0	2025-05-19
7.71.0	2 / 0	2025-05-15
7.70.0	2 / 0	2025-05-15
7.69.0	2 / 0	2025-05-04
7.68.0	2 / 0	2025-04-29

v7.110.0

1 finding

LOW No provenance attestation provenance

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

v7.109.0

1 finding

LOW No provenance attestation provenance

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

v7.108.0

1 finding

LOW No provenance attestation provenance

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

v7.107.0

1 finding

LOW No provenance attestation provenance

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

v7.106.0

1 finding

LOW No provenance attestation provenance

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

v7.105.0

1 finding

LOW No provenance attestation provenance

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

v7.104.0

1 finding

LOW No provenance attestation provenance

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

v7.103.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.102.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.101.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.100.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.99.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.98.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.97.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.96.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.95.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.94.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.93.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@frontegg/js' is 1 edit(s) away from popular package 'qs'.

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.

v7.92.0

1 finding

LOW No provenance attestation provenance

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

v7.91.0

1 finding

LOW No provenance attestation provenance

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

v7.90.0

1 finding

LOW No provenance attestation provenance

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

v7.89.0

1 finding

LOW No provenance attestation provenance

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

v7.88.0

1 finding

LOW No provenance attestation provenance

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

v7.87.0

1 finding

LOW No provenance attestation provenance

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

v7.86.0

1 finding

LOW No provenance attestation provenance

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

v7.85.0

1 finding

LOW No provenance attestation provenance

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

v7.84.0

1 finding

LOW No provenance attestation provenance

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

v7.83.0

1 finding

LOW No provenance attestation provenance

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

v7.82.0

1 finding

LOW No provenance attestation provenance

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

v7.81.0

1 finding

LOW No provenance attestation provenance

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

v7.80.0

1 finding

LOW No provenance attestation provenance

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

v7.79.0

1 finding

LOW No provenance attestation provenance

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

v7.78.0

1 finding

LOW No provenance attestation provenance

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

v7.77.0

1 finding

LOW No provenance attestation provenance

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

v7.76.0

1 finding

LOW No provenance attestation provenance

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

v7.75.0

1 finding

LOW No provenance attestation provenance

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

v7.74.0

1 finding

LOW No provenance attestation provenance

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

v7.73.0

1 finding

LOW No provenance attestation provenance

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

v7.72.0

1 finding

LOW No provenance attestation provenance

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

v7.71.0

1 finding

LOW No provenance attestation provenance

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

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

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

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