@talismn/keyring
<img src="talisman.svg" alt="Talisman" width="15%" align="right" />
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@talismn/crypto | AI (dependencies): Same-org dependency from TalismanSociety; consistent across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Talisman org packages consistently lack Sigstore provenance; stable false positive for this package family. | ai | |
| license | copyleft-license:GPL-3.0-or-later | AI (license): GPL-3.0-or-later is the declared license for the entire Talisman project; stable across versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 1 / 2 | |
| 1.0.10 | 1 / 2 | |
| 1.0.9 | 1 / 2 | |
| 1.0.8 | 1 / 2 | |
| 1.0.7 | 1 / 2 | |
| 1.0.6 | 1 / 9 | |
| 1.0.5 | 1 / 8 | |
| 1.0.4 | 1 / 8 | |
| 1.0.3 | 1 / 8 | |
| 1.0.2 | 1 / 8 | |
| 1.0.1 | 1 / 8 | |
| 1.0.0 | 1 / 8 |
v1.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.