@naviprotocol/lending
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): bignumber.js is a well-known, widely-used library with no malicious history; not a concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): NAVI Protocol SDK is a legitimate DeFi package; lack of provenance is common (~12% have it) and not a risk signal for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.4.6 | 4 / 7 | |
| 1.4.5 | 4 / 7 | |
| 1.4.4 | 4 / 7 | |
| 1.4.3 | 4 / 7 | |
| 1.4.2 | 4 / 7 | |
| 1.4.1 | 4 / 7 | |
| 1.3.10 | 4 / 7 | |
| 1.3.9 | 4 / 7 | |
| 1.3.8 | 4 / 7 | |
| 1.3.7 | 4 / 7 | |
| 1.3.6 | 4 / 7 | |
| 1.3.5 | 4 / 7 | |
| 1.3.4 | 4 / 7 | |
| 1.3.3 | 4 / 7 | |
| 1.3.2 | 4 / 7 | |
| 1.3.1 | 4 / 7 | |
| 1.3.0 | 4 / 7 | |
| 1.0.4 | 5 / 6 | |
| 1.0.1 | 5 / 6 | |
| 1.0.0 | 4 / 6 |
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.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.
v1.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexayan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: alexayan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.