manifold-3d
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:esbuild-plugin-text-replace | AI (dependencies): Build-tool plugin used in bundling workflow; low risk for this established package. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-text-replace | AI (phantom-deps): Build-tool plugin referenced in esbuild config; not a runtime import, stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clear repo; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Emscripten-generated WASM loader boilerplate; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a declared runtime dep used in the bin/manifold-cad CLI entry point. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.5.1 | 11 / 12 | |
| 3.5.0 | 11 / 12 | |
| 3.4.1 | 11 / 11 | |
| 3.4.0 | 10 / 11 | |
| 3.3.2 | 10 / 11 | |
| 3.3.1 | 10 / 11 | |
| 3.3.0 | 10 / 11 | |
| 3.2.1 | 0 / 1 | |
| 3.2.0 | 0 / 1 | |
| 3.1.1 | 0 / 1 | |
| 3.1.0 | 0 / 1 |
v3.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.