@script-development/fs-adapter-store
Reactive adapter-store pattern with domain state management and CRUD resource adapters
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 0 / 6 | |
| 0.1.6 | 0 / 6 | |
| 0.1.5 | 0 / 6 | |
| 0.1.4 | 0 / 6 | |
| 0.1.3 | 0 / 6 | |
| 0.1.2 | 0 / 6 | |
| 0.1.1 | 0 / 6 | |
| 0.1.0 | 0 / 6 |
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.