find-my-way
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used only in a benchmark utility script (benchmark/compare-branches.js), not in runtime library code. Stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in lib/constrainer.js is an intentional performance optimization compiling internally-constructed constraint logic, not user-controlled input. Standard pattern in high-performance routers. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 9.7.0 | 3 / 11 | |
| 9.6.0 | 3 / 11 | |
| 9.5.0 | 3 / 11 | |
| 9.4.0 | 3 / 11 | |
| 9.3.0 | 3 / 11 | |
| 9.2.0 | 3 / 11 | |
| 9.1.0 | 3 / 12 | |
| 9.0.1 | 3 / 12 |
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.