@pie-element/rubric
Rubric Scoring Interaction
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation via CI/CD confirms legitimate publish; no material changes from prior version. | ai | |
| provenance | no-provenance | AI (provenance): Established package ecosystem; lack of provenance is common and not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo element package; sparse README and no keywords are consistent across all versions of this package family. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in config files only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@emotion/style | AI (phantom-deps): Referenced in config files only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): Referenced in config files only; stable false positive for this monorepo package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 8.1.2 | 7 / 0 | |
| 8.1.1 | 7 / 0 | |
| 8.0.1 | 7 / 0 | |
| 8.0.0 | 7 / 0 | |
| 6.3.3 | 4 / 0 | |
| 0.1.0 | 12 / 5 |
v8.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.