@ff-labs/fff-bun
High-performance fuzzy file finder for Bun - perfect for LLM agent tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated pipeline. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI releases multiple platform packages in rapid succession; expected pattern for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires only in a test file to inject git env vars; standard test pattern, not a runtime risk. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 0 / 2 | |
| 0.9.2 | 0 / 2 | |
| 0.9.1 | 0 / 2 | |
| 0.9.0 | 0 / 2 | |
| 0.8.4 | 0 / 2 | |
| 0.8.1 | 0 / 2 | |
| 0.8.0 | 0 / 2 | |
| 0.7.2 | 0 / 2 | |
| 0.7.1 | 0 / 2 | |
| 0.7.0 | 0 / 2 | |
| 0.6.4 | 0 / 2 | |
| 0.6.3 | 0 / 2 | |
| 0.6.2 | 0 / 2 | |
| 0.6.1 | 0 / 2 | |
| 0.6.0 | 0 / 2 | |
| 0.5.2 | 0 / 2 | |
| 0.5.1 | 0 / 2 | |
| 0.5.0 | 0 / 2 | |
| 0.4.2 | 0 / 2 | |
| 0.4.0 | 0 / 2 |
v0.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-25. 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.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/dmtrKovalenko/fff.nvim/blob/4b13a91aa57c5e9ed32ee381d9ee521800818370/src/git-lifecycle.test.ts#L39 37 | cwd, 38 | stdio: "pipe", > 39 | env: { 40 | ...process.env, 41 | GIT_AUTHOR_NAME: "test",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.