@open-keystone/adapter-mongoose
KeystoneJS Mongoose Database adapter.
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 | no-provenance | AI (provenance): Publisher consistently publishes without provenance; not a risk signal for this scoped fork. | ai | |
| dependencies | unvetted-dep:@open-keystone/utils | AI (dependencies): Internal sibling dep in the open-keystone monorepo fork; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@open-keystone/keystone | AI (dependencies): Internal sibling dep in the open-keystone monorepo fork; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@open-keystone/fields-mongoid | AI (dependencies): Internal sibling dep in the open-keystone monorepo fork; expected pattern across all versions. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 13.0.26 | 6 / 3 | |
| 13.0.25 | 6 / 3 | |
| 13.0.24 | 6 / 3 | |
| 13.0.14 | 6 / 3 | |
| 13.0.13 | 6 / 3 | |
| 13.0.12 | 6 / 3 | |
| 13.0.11 | 6 / 3 | |
| 13.0.10 | 6 / 3 | |
| 13.0.9 | 6 / 3 | |
| 13.0.8 | 6 / 3 | |
| 13.0.7 | 6 / 3 | |
| 13.0.6 | 6 / 3 | |
| 13.0.5 | 6 / 3 | |
| 13.0.4 | 6 / 3 | |
| 13.0.3 | 6 / 3 | |
| 13.0.2 | 6 / 3 | |
| 13.0.1 | 6 / 3 | |
| 13.0.0 | 6 / 3 |
v13.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.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.
v13.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.