@talismn/on-chain-id
<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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated to GitHub Actions CI/CD with SLSA provenance; stable for this org's packages. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Build output change in monorepo; no suspicious content. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @talismn/crypto, a first-party Talisman package; not a suspicious third-party addition. | ai | |
| provenance | no-provenance | AI (provenance): Talisman monorepo packages consistently lack provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@talismn/util | AI (dependencies): Same-org sibling package from TalismanSociety; consistent namespace and SLSA-attested publisher. | ai | |
| dependencies | unvetted-dep:@talismn/crypto | AI (dependencies): Same-org sibling package from TalismanSociety; consistent namespace and SLSA-attested publisher. | ai | |
| provenance | slsa-provenance | AI (provenance): Published via CI/CD with Sigstore attestation; strong supply chain integrity for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 4 / 2 | |
| 0.2.12 | 4 / 2 | |
| 0.2.11 | 4 / 2 | |
| 0.2.10 | 4 / 2 | |
| 0.2.9 | 4 / 2 | |
| 0.2.8 | 4 / 2 | |
| 0.2.7 | 4 / 2 | |
| 0.2.6 | 4 / 2 | |
| 0.2.5 | 4 / 2 | |
| 0.2.4 | 4 / 7 | |
| 0.2.3 | 4 / 7 | |
| 0.2.2 | 4 / 7 | |
| 0.2.1 | 4 / 7 | |
| 0.2.0 | 4 / 7 | |
| 0.1.29 | 4 / 11 | |
| 0.1.28 | 4 / 11 | |
| 0.1.27 | 4 / 11 | |
| 0.1.26 | 4 / 11 | |
| 0.1.24 | 4 / 11 | |
| 0.1.23 | 4 / 11 | |
| 0.1.22 | 4 / 11 | |
| 0.1.21 | 3 / 11 | |
| 0.1.20 | 3 / 11 | |
| 0.1.19 | 3 / 11 | |
| 0.1.18 | 3 / 11 | |
| 0.1.17 | 3 / 11 | |
| 0.1.16 | 3 / 11 | |
| 0.1.15 | 3 / 11 | |
| 0.1.14 | 3 / 11 | |
| 0.1.13 | 3 / 11 | |
| 0.1.12 | 3 / 11 | |
| 0.1.11 | 3 / 11 | |
| 0.1.10 | 3 / 11 | |
| 0.1.9 | 3 / 11 | |
| 0.1.8 | 3 / 11 | |
| 0.1.7 | 3 / 11 | |
| 0.1.6 | 3 / 11 | |
| 0.1.5 | 3 / 11 | |
| 0.1.4 | 3 / 11 | |
| 0.1.3 | 3 / 11 | |
| 0.1.2 | 3 / 11 | |
| 0.1.1 | 3 / 11 |
v1.0.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.12
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.