@adobe/genstudio-extensibility-sdk
GenStudio Extensibility SDK
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@adobe/uix-core | AI (dependencies): Same-org Adobe dependency consistent with this SDK's documented UIX integration purpose. | ai | |
| dependencies | unvetted-dep:@adobe/uix-guest | AI (dependencies): Same-org Adobe dependency consistent with this SDK's documented UIX integration purpose. | ai | |
| provenance | no-provenance | AI (provenance): Adobe org package; absence of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@adobe/uix-guest | AI (phantom-deps): Same-org Adobe dep; may be re-exported or used indirectly — stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.7.0 | 3 / 12 | |
| 4.6.0 | 3 / 12 | |
| 4.5.1 | 3 / 12 | |
| 4.5.0 | 3 / 12 | |
| 4.4.0 | 3 / 12 | |
| 4.3.2 | 3 / 12 | |
| 4.3.1 | 3 / 12 | |
| 4.3.0 | 3 / 12 | |
| 4.2.3 | 3 / 11 | |
| 4.2.2 | 3 / 11 | |
| 4.2.1 | 3 / 11 | |
| 4.2.0 | 3 / 11 | |
| 4.1.0 | 3 / 11 | |
| 4.0.3 | 3 / 11 | |
| 4.0.2 | 3 / 11 | |
| 4.0.1 | 3 / 11 | |
| 4.0.0 | 3 / 11 |
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v4.3.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.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.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.
v4.0.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.
v4.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.