@frontegg/client
Frontegg Javascript Library for backend node servers
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Compiled dist import text not scannable; legitimate logging dep. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): Compiled dist; core auth SDK dependency. | ai | |
| phantom-deps | phantom-dep:@frontegg/entitlements-javascript-commons | AI (phantom-deps): Same-org scoped dep, compiled output. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Compiled dist import text not scannable; deps are legitimately used. | ai | |
| phantom-deps | phantom-dep:node-cache | AI (phantom-deps): Compiled dist; legitimate cache dep. | ai | |
| phantom-deps | phantom-dep:@slack/web-api | AI (phantom-deps): Likely legitimate optional integration dep; no malicious behavior indicated. | ai | |
| provenance | no-provenance | AI (provenance): Established Frontegg SDK; no provenance is consistent across all 189 versions and is not a risk indicator here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 5 / 26 | |
| 7.0.1 | 5 / 26 | |
| 7.0.0 | 5 / 26 | |
| 5.3.2 | 5 / 26 | |
| 5.3.1 | 5 / 26 | |
| 5.3.0 | 5 / 26 | |
| 5.2.1 | 5 / 26 | |
| 5.2.0 | 6 / 26 | |
| 5.1.2 | 5 / 25 | |
| 5.1.1 | 5 / 25 | |
| 5.1.0 | 5 / 25 | |
| 5.0.0 | 5 / 22 |
v7.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (guy_frontegg) than the most recent previously approved version (front-egg) on 2025-12-01, but guy_frontegg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (guy_frontegg) than the most recent previously approved version (front-egg) on 2025-12-01, but guy_frontegg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (guy_frontegg) than the most recent previously approved version (front-egg) on 2025-11-27, but guy_frontegg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.