@ifc-lite/sandbox
QuickJS-in-WASM sandboxed script execution for ifc-lite
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Young monorepo package; provenance absence is common and no other risk signals present. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 3 / 2 | |
| 1.14.0 | 3 / 2 | |
| 1.13.0 | 3 / 2 | |
| 1.11.5 | 3 / 2 | |
| 1.11.4 | 3 / 2 | |
| 1.11.1 | 3 / 2 | |
| 1.10.0 | 3 / 2 | |
| 1.9.0 | 3 / 2 | |
| 1.7.0 | 3 / 2 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.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.