@growthbook/growthbook
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): GrowthBook SDK is a well-established package; lack of provenance is common and not a security risk for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 1 / 29 | |
| 1.6.4 | 1 / 29 | |
| 1.6.3 | 1 / 29 | |
| 1.6.2 | 1 / 25 | |
| 1.6.1 | 1 / 25 | |
| 1.6.0 | 1 / 25 | |
| 1.5.1 | 1 / 25 | |
| 1.5.0 | 1 / 25 | |
| 1.4.1 | 1 / 25 | |
| 1.4.0 | 1 / 25 | |
| 1.3.1 | 1 / 25 | |
| 1.3.0 | 1 / 25 | |
| 1.2.1 | 1 / 25 | |
| 1.2.0 | 1 / 25 | |
| 1.1.0 | 1 / 25 | |
| 1.0.1 | 1 / 24 | |
| 1.0.0 | 1 / 24 |
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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 (jdorn) than the most recent previously approved version (bryce-fitzsimons) on 2024-12-04, but jdorn 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.3.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 (jdorn) than the most recent previously approved version (bryce-fitzsimons) on 2024-11-20, but jdorn 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.2.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 (bryce-fitzsimons) than the most recent previously approved version (jdorn) on 2024-10-09, but bryce-fitzsimons 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.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.