@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 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 7.20.0 | 2 / 0 | |
| 7.19.0 | 2 / 0 | |
| 7.18.0 | 2 / 0 | |
| 7.17.0 | 2 / 0 | |
| 7.16.0 | 2 / 0 | |
| 7.15.0 | 2 / 0 | |
| 7.14.0 | 2 / 0 | |
| 7.13.0 | 2 / 0 | |
| 7.12.0 | 2 / 0 | |
| 7.11.0 | 2 / 0 | |
| 7.10.0 | 2 / 0 | |
| 7.9.0 | 2 / 0 | |
| 7.8.0 | 2 / 0 | |
| 7.7.0 | 2 / 0 | |
| 7.6.0 | 2 / 0 | |
| 7.5.0 | 2 / 0 | |
| 7.4.0 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.2.0 | 2 / 0 | |
| 7.1.0 | 2 / 0 |
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.