@frontegg/nuxt
<p align="center"> <a href="https://www.frontegg.com/" rel="noopener" target="_blank"> <img style="margin-top:40px" height="50" src="https://frontegg.com/wp-content/uploads/2020/04/logo_frrontegg.svg" alt="Frontegg logo"> </a> </p> <h1 align="cent
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:next | AI (typosquat): @frontegg/nuxt is a scoped Frontegg SDK package, not a typosquat of 'next'; the edit-distance match is coincidental. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 4.12.0 | 1 / 0 | |
| 4.11.9 | 1 / 0 | |
| 4.11.8 | 1 / 0 | |
| 4.11.7 | 1 / 0 | |
| 4.11.6 | 1 / 0 | |
| 4.11.5 | 1 / 0 | |
| 4.11.4 | 1 / 0 | |
| 4.11.3 | 1 / 0 | |
| 4.11.2 | 1 / 0 | |
| 4.11.1 | 1 / 0 | |
| 4.11.0 | 1 / 0 | |
| 4.10.17 | 1 / 0 | |
| 4.10.16 | 1 / 0 | |
| 4.10.15 | 1 / 0 | |
| 4.10.14 | 1 / 0 | |
| 4.10.13 | 1 / 0 | |
| 4.10.12 | 1 / 0 | |
| 4.10.11 | 1 / 0 | |
| 4.10.10 | 1 / 0 | |
| 4.10.9 | 1 / 0 | |
| 4.10.8 | 1 / 0 | |
| 4.10.7 | 1 / 0 | |
| 4.10.6 | 1 / 0 | |
| 4.10.5 | 1 / 0 | |
| 4.10.4 | 1 / 0 | |
| 4.10.3 | 1 / 0 | |
| 4.10.2 | 1 / 0 | |
| 4.10.1 | 1 / 0 | |
| 4.10.0 | 1 / 0 | |
| 4.9.1 | 1 / 0 | |
| 4.9.0 | 1 / 0 | |
| 4.8.0 | 1 / 0 | |
| 4.7.2 | 1 / 0 | |
| 4.7.1 | 1 / 0 | |
| 4.7.0 | 1 / 0 | |
| 4.6.5 | 1 / 0 | |
| 4.6.4 | 1 / 0 | |
| 4.6.3 | 1 / 0 | |
| 4.6.2 | 1 / 0 | |
| 4.6.1 | 1 / 0 | |
| 4.6.0 | 1 / 0 | |
| 4.5.1 | 1 / 0 | |
| 4.5.0 | 1 / 0 | |
| 4.4.9 | 1 / 0 | |
| 4.4.8 | 1 / 0 | |
| 4.4.7 | 1 / 0 | |
| 4.4.6 | 1 / 0 | |
| 4.4.5 | 1 / 0 | |
| 4.4.4 | 1 / 0 | |
| 4.4.3 | 1 / 0 | |
| 4.4.2 | 1 / 0 |
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.