@injectivelabs/indexer-api
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Long-stale publisher change with no takedown; consistent with legitimate transfer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same maintainer transfer, corroborated by stale provenance signal. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with known publisher change, not new suspicious activity. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.11.54 | 2 / 0 | |
| 1.11.53 | 2 / 0 | |
| 1.11.52 | 2 / 0 | |
| 1.11.51 | 2 / 0 | |
| 1.11.50 | 2 / 0 | |
| 1.11.49 | 2 / 0 | |
| 1.11.48 | 2 / 0 | |
| 1.11.47 | 2 / 0 | |
| 1.11.46 | 2 / 0 | |
| 1.11.45 | 2 / 0 |
v1.11.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.53
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicolasbaum) than the most recent previously approved version (proofofze) on 2024-09-11, but nicolasbaum is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.52
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (proofofze) than the most recent previously approved version (nicolasbaum) on 2024-09-09, but proofofze is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.51
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicolasbaum) than the most recent previously approved version (proofofze) on 2024-09-09, but nicolasbaum is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.50
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (proofofze) than the most recent previously approved version (hmoragrega) on 2024-09-06, but proofofze is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.48
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hmoragrega) than the most recent previously approved version (proofofze) on 2024-08-07, but hmoragrega is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.47
2 findingsThis version was published by a different npm account (nicolasbaum) than the most recent previously approved version (proofofze) on 2024-07-30. It has since remained available on npm for 724 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.