@prairielearn/migrations
This package runs two types of database migrations:
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing is an improvement; consistent with PrairieLearn monorepo workflow adoption. | ai | |
| provenance | missing-githead | AI (provenance): SLSA attestation present; gitHead absence is a CI config artifact, not a supply chain risk for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): PrairieLearn org publishes via GitHub Actions; individual maintainer removal reflects CI-only publish model. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; no description is a stable characteristic across versions. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 7 / 8 | |
| 5.1.0 | 7 / 8 | |
| 5.0.8 | 7 / 8 | |
| 5.0.7 | 7 / 8 | |
| 5.0.6 | 7 / 8 | |
| 5.0.5 | 7 / 9 | |
| 5.0.4 | 7 / 10 | |
| 5.0.3 | 7 / 10 | |
| 5.0.2 | 7 / 10 | |
| 5.0.1 | 7 / 10 | |
| 5.0.0 | 7 / 10 | |
| 4.0.5 | 7 / 10 | |
| 4.0.4 | 7 / 9 | |
| 4.0.3 | 7 / 9 |
v5.1.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] 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.
v5.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
2 findingsThis version was published by a different npm account than previous versions on 2025-12-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.