@prairielearn/express-test-utils
13
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
nwalters512mwest1066
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Types package used by convention, not directly imported. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo CI publish quirk, no behavioral change in diff. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 1 / 3 | |
| 2.0.11 | 1 / 3 | |
| 2.0.10 | 1 / 2 | |
| 2.0.9 | 1 / 2 | |
| 2.0.8 | 1 / 2 | |
| 2.0.7 | 1 / 1 | |
| 2.0.6 | 1 / 1 | |
| 2.0.5 | 1 / 0 | |
| 2.0.4 | 1 / 0 | |
| 2.0.3 | 1 / 0 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 |
v2.0.12
2 findings
HIGH
Missing gitHead — previous versions had it
provenance
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.