@digabi/exam-engine-generator
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-removed | AI (maintainer-change): Long-established org package published via GitHub Actions CI with SLSA provenance; maintainer rotation is expected for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): SLSA provenance attestation present; no code/script changes; consistent with legitimate org maintainer addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped org package with 483 versions; sparse metadata is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal tooling package; not a malice signal. | ai | |
| dependencies | unvetted-dep:libxmljs2 | AI (dependencies): libxmljs2 is a known XML parsing library; its use in an exam engine generator is expected and stable across versions. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 23.25.0 | 3 / 0 | |
| 23.24.3 | 3 / 0 | |
| 23.24.2 | 3 / 0 | |
| 23.24.1 | 3 / 0 | |
| 23.24.0 | 3 / 0 | |
| 23.23.0 | 3 / 0 | |
| 23.22.4 | 3 / 0 | |
| 23.22.3 | 3 / 0 | |
| 23.22.2 | 3 / 0 | |
| 23.22.1 | 3 / 0 | |
| 23.22.0 | 3 / 0 | |
| 23.21.0 | 3 / 0 | |
| 23.20.6 | 3 / 0 | |
| 23.20.5 | 3 / 0 | |
| 23.20.4 | 3 / 0 | |
| 23.20.3 | 3 / 0 | |
| 23.20.2 | 3 / 0 | |
| 23.20.1 | 3 / 0 | |
| 23.20.0 | 3 / 0 | |
| 23.19.3 | 3 / 0 | |
| 23.19.2 | 3 / 0 | |
| 23.19.1 | 3 / 0 | |
| 23.19.0 | 3 / 0 | |
| 23.18.0 | 3 / 0 | |
| 23.17.0 | 3 / 0 | |
| 23.16.0 | 3 / 0 | |
| 23.15.2 | 3 / 0 | |
| 23.15.1 | 3 / 0 | |
| 23.15.0 | 3 / 0 | |
| 23.14.5 | 3 / 0 | |
| 23.14.4 | 3 / 0 | |
| 23.14.3 | 3 / 0 | |
| 23.14.2 | 3 / 0 | |
| 23.14.1 | 3 / 0 | |
| 23.14.0 | 3 / 0 | |
| 23.13.6 | 3 / 0 | |
| 23.13.4 | 3 / 0 | |
| 23.13.3 | 3 / 0 | |
| 23.13.2 | 3 / 0 | |
| 23.13.1 | 3 / 0 |
v23.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.20.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.19.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.14.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.