helper-related
Template helper for generating a list of links to the homepages of related GitHub/npm projects.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lazy-cache | AI (phantom-deps): lazy-cache is a jonschlinkert idiom for lazy-loading deps; static import analysis won't see direct requires. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:get-pkgs | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai | |
| phantom-deps | phantom-dep:get-value | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai | |
| phantom-deps | phantom-dep:arr-filter | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai | |
| phantom-deps | phantom-dep:is-valid-glob | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai | |
| phantom-deps | phantom-dep:extend-shallow | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai | |
| phantom-deps | phantom-dep:async-array-reduce | AI (phantom-deps): Dependency loaded via lazy-cache pattern; not directly imported but legitimately used. Stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 4 / 5 | |
| 0.15.2 | 6 / 6 | |
| 0.15.1 | 6 / 6 | |
| 0.15.0 | 6 / 6 | |
| 0.14.1 | 13 / 6 | |
| 0.14.0 | 11 / 6 | |
| 0.13.2 | 9 / 6 | |
| 0.13.1 | 9 / 5 | |
| 0.13.0 | 9 / 5 | |
| 0.12.1 | 9 / 5 | |
| 0.12.0 | 9 / 5 | |
| 0.11.2 | 7 / 5 | |
| 0.11.1 | 7 / 5 | |
| 0.11.0 | 7 / 5 | |
| 0.10.0 | 9 / 2 | |
| 0.9.0 | 9 / 2 | |
| 0.8.0 | 8 / 2 | |
| 0.7.1 | 6 / 2 | |
| 0.7.0 | 6 / 2 | |
| 0.6.2 | 5 / 2 | |
| 0.6.1 | 5 / 2 | |
| 0.6.0 | 5 / 2 | |
| 0.4.0 | 4 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.0 | 4 / 2 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
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.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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.