@open-keystone/test-utils
Common utilities used while testing @open-keystone/* packages.
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 | dormant-publish | AI (publish-pattern): Publisher has 11 approved packages and SLSA provenance; dormancy consistent with infrequent maintenance cadence, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals elevate this. | ai | |
| phantom-deps | phantom-dep:mongodb-memory-server | AI (phantom-deps): mongodb-memory-server is a legitimate runtime dep declared in package.json; used as a test utility, not directly imported in source files. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 14.0.24 | 9 / 0 | |
| 14.0.23 | 9 / 0 | |
| 14.0.22 | 9 / 0 | |
| 14.0.20 | 9 / 0 | |
| 14.0.11 | 8 / 0 | |
| 14.0.10 | 8 / 0 | |
| 14.0.9 | 8 / 0 | |
| 14.0.8 | 8 / 0 | |
| 14.0.7 | 8 / 0 | |
| 14.0.6 | 8 / 0 | |
| 14.0.5 | 8 / 0 | |
| 14.0.4 | 8 / 0 | |
| 14.0.3 | 8 / 0 | |
| 14.0.2 | 8 / 0 | |
| 14.0.1 | 8 / 0 | |
| 14.0.0 | 8 / 0 |
v14.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.