piral-core
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in codegen/template engine (lib/codegen.js); standard pattern for this type of package, stable across versions. | ai | |
| dependencies | unvetted-dep:piral-base | AI (dependencies): Sibling package from same piral org; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:piral-debug-utils | AI (dependencies): Sibling package from same piral org; not an independent third-party risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 3 / 8 | |
| 1.10.3 | 3 / 8 | |
| 1.10.0 | 3 / 8 | |
| 1.9.2 | 3 / 8 | |
| 1.9.1 | 3 / 8 | |
| 1.9.0 | 3 / 8 |
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
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.