@frontegg/entitlements-javascript-commons
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
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 0 / 17 | |
| 1.2.0 | 0 / 17 | |
| 1.1.5 | 0 / 17 | |
| 1.1.3 | 0 / 17 | |
| 1.1.2 | 0 / 17 | |
| 1.1.1 | 0 / 17 | |
| 1.1.0 | 0 / 17 | |
| 1.0.1 | 0 / 17 | |
| 1.0.0 | 0 / 17 |
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage 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 2024-01-09, 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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.