@open-keystone/keystone
The main @open-keystone class & CLI. This is where the magic happens.
4
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
open-condo-software
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): SLSA provenance attestation confirms CI/CD publish; dormancy is not indicative of takeover here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): CLI command-loader reads filenames from a local directory; not user-controlled arbitrary module loading. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 19.4.31 | 31 / 3 | |
| 19.4.30 | 31 / 3 | |
| 19.4.25 | 32 / 4 | |
| 19.4.0 | 30 / 4 |
v19.4.31
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v19.4.30
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v19.4.25
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v19.4.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.