tapable
Just a little module for plugins.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): tapable's HookCodeFactory uses new Function() as its core mechanism for dynamic hook code generation — this is fundamental, documented behavior stable across all versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 2.3.3 | 0 / 13 | |
| 2.3.2 | 0 / 11 | |
| 2.3.1 | 0 / 11 | |
| 2.2.1 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.1 | 0 / 6 | |
| 2.1.0 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.1.3 | 0 / 7 | |
| 1.1.2 | 0 / 7 | |
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 7 | |
| 1.0.0 | 0 / 6 | |
| 0.2.9 | 0 / 2 | |
| 0.2.8 | 0 / 2 | |
| 0.2.7 | 0 / 2 | |
| 0.2.6 | 0 / 2 | |
| 0.2.5 | 0 / 2 | |
| 0.2.4 | 0 / 2 | |
| 0.2.3 | 0 / 2 | |
| 0.2.2 | 0 / 2 | |
| 0.2.1 | 0 / 2 | |
| 0.1.10 | 0 / 2 | |
| 0.1.9 | 0 / 2 | |
| 0.1.8 | 0 / 2 | |
| 0.1.7 | 0 / 2 | |
| 0.1.6 | 0 / 2 | |
| 0.1.5 | 0 / 2 | |
| 0.1.4 | 0 / 2 | |
| 0.1.3 | 0 / 2 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.