@digabi/exam-engine-rendering
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 | new-deps-added | AI (publish-pattern): Routine dep swap (child-process-promise → promisify-child-process); established publisher with long clean history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): CI/CD-published package with SLSA provenance; maintainer churn in an org context is routine, not a takeover indicator. | ai | |
| dependencies | unvetted-dep:react-router5 | AI (dependencies): react-router5 is a legitimate routing library; stable dependency across this package's history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-lived scoped package in an active monorepo; missing metadata is a style choice, not a spam indicator. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Package has SLSA provenance; maintainer addition appears to be a legitimate org change for this long-established package. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): Build tool dep used via less-loader config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Loaded via config/convention in rendering pipeline, not direct import. | ai | |
| phantom-deps | phantom-dep:dexie | AI (phantom-deps): Likely loaded at runtime via framework convention, not direct import. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Used via postcss-loader config; indirect usage is expected. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped; loaded by babel-loader convention. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped; loaded by babel transform convention. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 23.24.3 | 33 / 0 | |
| 23.24.2 | 33 / 0 | |
| 23.24.1 | 33 / 0 | |
| 23.24.0 | 33 / 0 | |
| 23.23.0 | 33 / 0 | |
| 23.22.4 | 33 / 0 | |
| 23.22.3 | 33 / 0 | |
| 23.22.2 | 33 / 0 | |
| 23.22.1 | 33 / 0 | |
| 23.22.0 | 33 / 0 | |
| 23.21.0 | 33 / 0 | |
| 23.20.6 | 33 / 0 | |
| 23.20.1 | 33 / 0 | |
| 23.19.2 | 33 / 0 | |
| 23.19.1 | 33 / 0 | |
| 23.19.0 | 33 / 0 | |
| 23.16.0 | 33 / 0 | |
| 23.14.3 | 33 / 0 | |
| 23.14.2 | 33 / 0 | |
| 23.14.1 | 33 / 0 | |
| 23.13.4 | 33 / 0 | |
| 23.13.3 | 33 / 0 | |
| 23.13.2 | 33 / 0 | |
| 23.13.1 | 33 / 0 |
v23.24.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.24.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.22.2
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.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.13.3
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.
v23.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.