@digabi/exam-engine-mastering
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Established org package with SLSA provenance; maintainer addition appears to be a legitimate org change. | ai | |
| dependencies | unvetted-dep:ffprobe | AI (dependencies): ffprobe is a legitimate media-probing library; expected for exam-engine mastering use case. | ai | |
| dependencies | unvetted-dep:libxmljs2 | AI (dependencies): libxmljs2 is a well-known XML parsing library; appropriate for exam content processing. | ai | |
| dependencies | unvetted-dep:mathjax-node | AI (dependencies): mathjax-node is the standard server-side MathJax renderer; expected in an exam engine. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal tooling package from Finland's Matriculation Examination Board; metadata gaps are cosmetic, not indicative of spam/malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across 573 versions of this internal tooling package; not a malware signal. | ai | |
| phantom-deps | phantom-dep:@digabi/exam-engine-rendering | AI (phantom-deps): Same-org sibling package; declared as a runtime dep and expected not to be directly imported in this mastering package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 23.23.0 | 11 / 0 | |
| 23.22.4 | 11 / 0 | |
| 23.22.1 | 11 / 0 | |
| 23.22.0 | 11 / 0 | |
| 23.21.0 | 11 / 0 | |
| 23.20.6 | 11 / 0 | |
| 23.14.4 | 11 / 0 | |
| 23.14.1 | 11 / 0 | |
| 23.13.2 | 11 / 0 |
v23.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.22.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.20.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.