@learncard/sss-key-manager
Shamir Secret Sharing key manager for LearnCard - replaces Web3Auth SFA
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@noble/ed25519 | AI (phantom-deps): Declared runtime dep; likely used in bundled output rather than direct import in source. | ai | |
| phantom-deps | phantom-dep:@learncard/types | AI (phantom-deps): Same-org type dependency; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 5 / 9 | |
| 0.1.10 | 5 / 9 | |
| 0.1.9 | 5 / 9 | |
| 0.1.8 | 5 / 9 | |
| 0.1.7 | 5 / 9 | |
| 0.1.6 | 5 / 9 | |
| 0.1.4 | 5 / 9 | |
| 0.1.3 | 5 / 9 | |
| 0.1.0 | 5 / 9 |
v0.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.