@talismn/token-rates
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): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; consistent with org-level automation. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; package has a clear repo URL and long publish history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is expected for internal scoped packages in the Talisman ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across Talisman monorepo packages; not a malice indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.0.21 | 1 / 2 | |
| 3.0.20 | 1 / 2 | |
| 3.0.19 | 1 / 2 | |
| 3.0.18 | 1 / 2 | |
| 3.0.17 | 1 / 2 | |
| 3.0.16 | 1 / 2 | |
| 3.0.15 | 1 / 7 | |
| 3.0.14 | 1 / 7 | |
| 3.0.13 | 1 / 7 | |
| 3.0.12 | 1 / 7 | |
| 3.0.11 | 1 / 7 | |
| 3.0.10 | 1 / 7 | |
| 3.0.9 | 1 / 7 | |
| 3.0.8 | 1 / 7 | |
| 3.0.7 | 1 / 7 | |
| 3.0.5 | 1 / 7 | |
| 3.0.4 | 1 / 7 | |
| 3.0.3 | 1 / 7 | |
| 3.0.2 | 2 / 7 | |
| 3.0.1 | 2 / 7 | |
| 3.0.0 | 2 / 7 |
v3.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.17
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. 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.
v3.0.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. 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.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.