@agent-scope/render
Render paths for React components: Satori (simple/flexbox) and Playwright BrowserPool (complex)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:satori | AI (dependencies): satori is a legitimate Vercel OSS library for SVG rendering; expected dependency for this render package. | ai | |
| provenance | no-provenance | AI (provenance): Absence of provenance is common; no other risk signals elevate this for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped package with coherent description and deps; missing metadata is a hygiene issue, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/build dep referenced in config; not directly imported in source is expected for this render utility. | ai | |
| phantom-deps | phantom-dep:@fontsource/inter | AI (phantom-deps): Font package referenced in config/build setup only; phantom-dep false positive for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.25.3 | 8 / 7 | |
| 1.25.2 | 8 / 7 | |
| 1.25.1 | 8 / 7 | |
| 1.24.0 | 8 / 7 | |
| 1.23.0 | 8 / 7 | |
| 1.22.0 | 8 / 7 | |
| 1.21.10 | 8 / 7 | |
| 1.21.9 | 8 / 7 | |
| 1.21.5 | 8 / 7 | |
| 1.21.3 | 8 / 7 | |
| 1.20.19 | 8 / 7 | |
| 1.20.16 | 8 / 7 | |
| 1.20.15 | 8 / 7 | |
| 1.20.13 | 8 / 7 | |
| 1.20.12 | 8 / 7 | |
| 1.20.9 | 8 / 7 | |
| 1.20.7 | 8 / 7 | |
| 1.20.6 | 8 / 7 | |
| 1.20.3 | 8 / 7 | |
| 1.20.2 | 8 / 7 | |
| 1.17.2 | 8 / 7 | |
| 1.16.0 | 8 / 7 | |
| 1.12.0 | 8 / 7 | |
| 1.11.0 | 8 / 7 | |
| 1.9.0 | 8 / 7 | |
| 1.7.0 | 8 / 7 | |
| 1.4.0 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.2 | 8 / 7 | |
| 1.0.1 | 8 / 7 |
v1.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.