@forwardimpact/libwiki
Wiki lifecycle primitives — stable memory for agent teams so coordination persists across sessions.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread is passed to a git subprocess for token injection — standard CLI pattern, not exfiltration. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.2.24 | 6 / 1 | |
| 0.2.23 | 6 / 1 | |
| 0.2.22 | 6 / 1 | |
| 0.2.21 | 6 / 1 | |
| 0.2.20 | 6 / 1 | |
| 0.2.19 | 6 / 1 | |
| 0.2.18 | 6 / 1 | |
| 0.2.17 | 6 / 1 | |
| 0.2.16 | 6 / 1 | |
| 0.2.15 | 6 / 1 | |
| 0.2.14 | 6 / 1 | |
| 0.2.13 | 6 / 1 | |
| 0.2.12 | 6 / 1 | |
| 0.2.11 | 6 / 1 | |
| 0.2.10 | 6 / 1 | |
| 0.2.9 | 5 / 1 | |
| 0.2.8 | 5 / 1 | |
| 0.2.7 | 5 / 1 | |
| 0.2.6 | 5 / 1 | |
| 0.2.5 | 4 / 1 | |
| 0.2.4 | 4 / 1 | |
| 0.2.3 | 4 / 1 | |
| 0.2.2 | 4 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.5 | 4 / 1 | |
| 0.1.3 | 3 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.1 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v0.2.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/forwardimpact/monorepo/blob/09702838cd2cef6590b5df119677013c36869f08/src/wiki-repo.js#L164 162 | // expansion finds it even when the resolver pulled from `.env` or 163 | // `gh auth token` rather than the ambient process env. > 164 | const env = token ? { ...process.env, GH_TOKEN: token } : undefined; 165 | return spawnSync("git", fullArgs, { stdio: "pipe", env }); 166 | }
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.