@frontegg/js
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
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 | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Same scoped-package false positive pattern; not a typosquat of jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same scoped-package false positive pattern; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Same scoped-package false positive pattern; not a typosquat of rxjs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same scoped-package false positive pattern; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same scoped-package false positive pattern; not a typosquat of ajv. | ai |
Versions (showing 100 of 120)
| Version | Deps | Published |
|---|---|---|
| 7.121.0 | 2 / 0 | |
| 7.120.0 | 2 / 0 | |
| 7.119.0 | 2 / 0 | |
| 7.118.0 | 2 / 0 | |
| 7.117.0 | 2 / 0 | |
| 7.116.0 | 2 / 0 | |
| 7.115.0 | 2 / 0 | |
| 7.114.0 | 2 / 0 | |
| 7.113.0 | 2 / 0 | |
| 7.112.0 | 2 / 0 | |
| 7.111.0 | 2 / 0 | |
| 7.110.0 | 2 / 0 | |
| 7.109.0 | 2 / 0 | |
| 7.108.0 | 2 / 0 | |
| 7.107.0 | 2 / 0 | |
| 7.106.0 | 2 / 0 | |
| 7.105.0 | 2 / 0 | |
| 7.104.0 | 2 / 0 | |
| 7.103.0 | 2 / 0 | |
| 7.102.0 | 2 / 0 | |
| 7.101.0 | 2 / 0 | |
| 7.100.0 | 2 / 0 | |
| 7.99.0 | 2 / 0 | |
| 7.98.0 | 2 / 0 | |
| 7.97.0 | 2 / 0 | |
| 7.96.0 | 2 / 0 | |
| 7.95.0 | 2 / 0 | |
| 7.94.0 | 2 / 0 | |
| 7.93.0 | 2 / 0 | |
| 7.92.0 | 2 / 0 | |
| 7.91.0 | 2 / 0 | |
| 7.90.0 | 2 / 0 | |
| 7.89.0 | 2 / 0 | |
| 7.88.0 | 2 / 0 | |
| 7.87.0 | 2 / 0 | |
| 7.86.0 | 2 / 0 | |
| 7.85.0 | 2 / 0 | |
| 7.84.0 | 2 / 0 | |
| 7.83.0 | 2 / 0 | |
| 7.82.0 | 2 / 0 | |
| 7.81.0 | 2 / 0 | |
| 7.80.0 | 2 / 0 | |
| 7.79.0 | 2 / 0 | |
| 7.78.0 | 2 / 0 | |
| 7.77.0 | 2 / 0 | |
| 7.76.0 | 2 / 0 | |
| 7.75.0 | 2 / 0 | |
| 7.74.0 | 2 / 0 | |
| 7.73.0 | 2 / 0 | |
| 7.72.0 | 2 / 0 | |
| 7.71.0 | 2 / 0 | |
| 7.70.0 | 2 / 0 | |
| 7.69.0 | 2 / 0 | |
| 7.68.0 | 2 / 0 | |
| 7.67.0 | 2 / 0 | |
| 7.66.0 | 2 / 0 | |
| 7.65.0 | 2 / 0 | |
| 7.64.0 | 2 / 0 | |
| 7.63.0 | 2 / 0 | |
| 7.62.0 | 2 / 0 | |
| 7.61.0 | 2 / 0 | |
| 7.60.0 | 2 / 0 | |
| 7.59.0 | 2 / 0 | |
| 7.58.0 | 2 / 0 | |
| 7.57.0 | 2 / 0 | |
| 7.56.0 | 2 / 0 | |
| 7.55.0 | 2 / 0 | |
| 7.54.0 | 2 / 0 | |
| 7.53.0 | 2 / 0 | |
| 7.52.0 | 2 / 0 | |
| 7.51.0 | 2 / 0 | |
| 7.50.0 | 2 / 0 | |
| 7.49.0 | 2 / 0 | |
| 7.48.0 | 2 / 0 | |
| 7.47.0 | 2 / 0 | |
| 7.45.0 | 2 / 0 | |
| 7.44.0 | 2 / 0 | |
| 7.43.0 | 2 / 0 | |
| 7.42.0 | 2 / 0 | |
| 7.41.0 | 2 / 0 | |
| 7.40.0 | 2 / 0 | |
| 7.39.0 | 2 / 0 | |
| 7.38.0 | 2 / 0 | |
| 7.37.0 | 2 / 0 | |
| 7.36.0 | 2 / 0 | |
| 7.35.0 | 2 / 0 | |
| 7.34.0 | 2 / 0 | |
| 7.33.0 | 2 / 0 | |
| 7.32.0 | 2 / 0 | |
| 7.31.0 | 2 / 0 | |
| 7.30.0 | 2 / 0 | |
| 7.29.0 | 2 / 0 | |
| 7.28.0 | 2 / 0 | |
| 7.27.0 | 2 / 0 | |
| 7.26.0 | 2 / 0 | |
| 7.25.0 | 2 / 0 | |
| 7.24.0 | 2 / 0 | |
| 7.23.0 | 2 / 0 | |
| 7.22.0 | 2 / 0 | |
| 7.21.0 | 2 / 0 |
v7.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.