@lifi/tenderlysim
Helpers to simulate lifi quotes
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation and GitHub Actions publisher confirm legitimate CI/CD release; dormancy is not indicative of takeover here. | ai | |
| dependencies | unvetted-dep:resolve-tspaths | AI (dependencies): resolve-tspaths is a build-time TS path resolver, not a runtime attack surface; stable use across this package's versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate LI.FI org package with 90 versions and SLSA provenance; README style is org convention, not spam. | ai | |
| phantom-deps | phantom-dep:tsconfig-paths | AI (phantom-deps): tsconfig-paths is a build-time path resolver referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:resolve-tspaths | AI (phantom-deps): resolve-tspaths is invoked via build script, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/memoizee | AI (phantom-deps): Type-only package; not directly imported by design. Stable false positive. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.0.65 | 8 / 27 | |
| 0.0.64 | 8 / 27 | |
| 0.0.63 | 8 / 27 | |
| 0.0.62 | 8 / 27 | |
| 0.0.61 | 8 / 27 | |
| 0.0.58 | 8 / 27 | |
| 0.0.57 | 8 / 27 | |
| 0.0.56 | 8 / 27 | |
| 0.0.55 | 8 / 27 | |
| 0.0.54 | 8 / 27 | |
| 0.0.53 | 8 / 27 | |
| 0.0.52 | 8 / 27 | |
| 0.0.51 | 8 / 27 | |
| 0.0.50 | 8 / 27 | |
| 0.0.49 | 8 / 27 | |
| 0.0.48 | 8 / 27 | |
| 0.0.47 | 8 / 27 | |
| 0.0.46 | 8 / 27 | |
| 0.0.45 | 8 / 27 | |
| 0.0.44 | 8 / 27 | |
| 0.0.43 | 8 / 27 | |
| 0.0.42 | 8 / 27 | |
| 0.0.41 | 8 / 27 | |
| 0.0.40 | 8 / 27 | |
| 0.0.39 | 8 / 27 | |
| 0.0.38 | 8 / 27 | |
| 0.0.37 | 8 / 27 | |
| 0.0.36 | 8 / 27 | |
| 0.0.35 | 8 / 27 | |
| 0.0.34 | 8 / 27 | |
| 0.0.33 | 8 / 27 | |
| 0.0.32 | 8 / 27 | |
| 0.0.31 | 8 / 27 | |
| 0.0.30 | 8 / 27 | |
| 0.0.29 | 8 / 27 | |
| 0.0.28 | 8 / 27 | |
| 0.0.27 | 8 / 27 | |
| 0.0.26 | 8 / 27 | |
| 0.0.25 | 8 / 27 | |
| 0.0.24 | 8 / 27 | |
| 0.0.23 | 8 / 27 | |
| 0.0.22 | 8 / 27 | |
| 0.0.21 | 8 / 27 | |
| 0.0.20 | 8 / 27 | |
| 0.0.19 | 8 / 27 | |
| 0.0.17 | 8 / 27 | |
| 0.0.16 | 8 / 27 | |
| 0.0.14 | 8 / 27 | |
| 0.0.2 | 8 / 27 | |
| 0.0.1 | 8 / 23 |
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.