@akinon/projectzero
CLI tool to manage your Project Zero Next project
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads theme config from a filesystem path — not user-controlled arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in a codemod utility script, not in install hooks or runtime critical paths. | ai | |
| phantom-deps | phantom-dep:temp | AI (phantom-deps): temp is a declared dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 2.0.35 | 6 / 3 | |
| 2.0.34 | 6 / 3 | |
| 2.0.33 | 6 / 3 | |
| 2.0.32 | 6 / 3 | |
| 2.0.31 | 6 / 3 | |
| 2.0.30 | 6 / 3 | |
| 2.0.29 | 6 / 3 | |
| 2.0.28 | 6 / 3 | |
| 2.0.27 | 6 / 3 | |
| 2.0.26 | 6 / 3 | |
| 2.0.25 | 6 / 3 | |
| 2.0.24 | 6 / 3 | |
| 2.0.23 | 6 / 3 | |
| 2.0.22 | 6 / 3 | |
| 2.0.21 | 6 / 3 | |
| 2.0.20 | 6 / 3 | |
| 2.0.19 | 6 / 3 | |
| 2.0.18 | 6 / 3 | |
| 2.0.17 | 6 / 3 | |
| 2.0.16 | 6 / 3 | |
| 2.0.15 | 6 / 3 | |
| 2.0.14 | 6 / 3 | |
| 2.0.13 | 6 / 3 | |
| 2.0.12 | 6 / 3 | |
| 2.0.11 | 6 / 3 | |
| 2.0.10 | 6 / 3 | |
| 2.0.9 | 6 / 3 | |
| 2.0.8 | 6 / 3 | |
| 2.0.7 | 6 / 3 | |
| 2.0.6 | 6 / 3 | |
| 2.0.5 | 6 / 3 | |
| 2.0.4 | 6 / 3 | |
| 2.0.3 | 6 / 3 | |
| 2.0.2 | 6 / 3 | |
| 2.0.1 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.126.6 | 6 / 3 | |
| 1.126.5 | 6 / 3 | |
| 1.126.4 | 6 / 3 | |
| 1.126.3 | 6 / 3 | |
| 1.126.2 | 6 / 3 | |
| 1.126.1 | 6 / 3 | |
| 1.126.0 | 6 / 3 | |
| 1.125.2 | 6 / 3 | |
| 1.125.1 | 6 / 3 | |
| 1.125.0 | 6 / 3 | |
| 1.124.0 | 6 / 3 | |
| 1.123.0 | 6 / 3 | |
| 1.122.0 | 6 / 3 | |
| 1.121.0 | 6 / 3 | |
| 1.120.0 | 6 / 3 | |
| 1.119.0 | 6 / 3 | |
| 1.118.0 | 6 / 3 | |
| 1.117.0 | 6 / 3 | |
| 1.116.0 | 6 / 3 | |
| 1.115.0 | 6 / 3 | |
| 1.114.0 | 6 / 3 | |
| 1.113.0 | 6 / 3 | |
| 1.112.0 | 6 / 3 | |
| 1.111.0 | 6 / 3 | |
| 1.110.0 | 6 / 3 | |
| 1.32.0 | 5 / 3 | |
| 1.31.1 | 5 / 3 | |
| 1.31.0 | 5 / 3 | |
| 1.30.2 | 5 / 3 | |
| 1.30.1 | 5 / 3 | |
| 1.30.0 | 4 / 3 | |
| 1.29.0 | 4 / 2 | |
| 1.27.0 | 4 / 2 | |
| 1.26.0 | 4 / 2 | |
| 1.25.0 | 4 / 2 | |
| 1.24.1 | 4 / 2 | |
| 1.24.0 | 4 / 2 | |
| 1.23.0 | 4 / 2 | |
| 1.22.0 | 4 / 2 | |
| 1.21.0 | 4 / 2 | |
| 1.20.0 | 4 / 2 | |
| 1.19.4 | 4 / 2 | |
| 1.19.3 | 4 / 2 | |
| 1.19.2 | 4 / 2 | |
| 1.19.1 | 4 / 2 | |
| 1.19.0 | 4 / 2 | |
| 1.18.0 | 4 / 2 | |
| 1.17.1 | 4 / 2 | |
| 1.17.0 | 4 / 2 | |
| 1.16.3 | 4 / 2 | |
| 1.16.2 | 4 / 2 | |
| 1.16.1 | 4 / 2 | |
| 1.16.0 | 4 / 2 | |
| 1.15.0 | 4 / 2 | |
| 1.14.1 | 4 / 2 | |
| 1.14.0 | 4 / 2 | |
| 1.13.1 | 4 / 2 | |
| 1.13.0 | 4 / 2 | |
| 1.12.0 | 4 / 2 | |
| 1.11.0 | 4 / 2 | |
| 1.10.0 | 3 / 1 | |
| 1.9.0 | 3 / 1 | |
| 1.8.0 | 3 / 1 | |
| 1.7.0 | 3 / 1 |
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.126.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.126.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.126.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.125.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.124.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.123.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.122.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.111.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.