@majikah/majik-key
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Manual-to-CI/CD provenance transition, not an account compromise indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds established @noble/@scure crypto libs consistent with package's crypto-key purpose. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 15 / 6 | |
| 0.3.2 | 15 / 6 | |
| 0.3.1 | 15 / 6 | |
| 0.3.0 | 15 / 6 | |
| 0.2.14 | 15 / 6 | |
| 0.2.13 | 15 / 6 | |
| 0.2.12 | 13 / 5 | |
| 0.2.11 | 13 / 4 | |
| 0.2.10 | 13 / 4 | |
| 0.2.9 | 13 / 4 | |
| 0.2.7 | 13 / 1 | |
| 0.2.6 | 13 / 1 | |
| 0.2.5 | 13 / 1 | |
| 0.2.4 | 13 / 1 | |
| 0.2.3 | 12 / 1 | |
| 0.2.2 | 12 / 1 | |
| 0.2.1 | 12 / 1 | |
| 0.2.0 | 12 / 1 | |
| 0.1.10 | 12 / 1 | |
| 0.1.9 | 12 / 1 | |
| 0.1.8 | 11 / 1 | |
| 0.1.7 | 11 / 1 | |
| 0.1.6 | 11 / 1 | |
| 0.1.5 | 11 / 1 | |
| 0.1.4 | 11 / 1 | |
| 0.1.3 | 11 / 1 | |
| 0.1.2 | 11 / 1 | |
| 0.1.1 | 9 / 1 |
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.13
2 findingsThis version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.