@donotdev/functions
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:env-spread | AI (semgrep): Fires in test files saving/restoring process.env — standard Jest pattern, not a secret leak. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Fires in a test asserting file:///etc/passwd is rejected as invalid URL — not credential harvesting. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fires in minified Firebase/AI SDK bundle; no exfiltration pattern visible in context. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in minified supabase bundle; context shows normal SDK code, no payload decoding. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.1.42 | 3 / 0 | |
| 0.0.19 | 3 / 0 | |
| 0.0.18 | 3 / 0 | |
| 0.0.17 | 3 / 0 | |
| 0.0.16 | 3 / 0 | |
| 0.0.15 | 3 / 0 | |
| 0.0.14 | 3 / 0 | |
| 0.0.13 | 3 / 0 | |
| 0.0.12 | 3 / 0 | |
| 0.0.11 | 3 / 0 | |
| 0.0.10 | 2 / 0 | |
| 0.0.9 | 2 / 0 | |
| 0.0.8 | 2 / 0 | |
| 0.0.7 | 2 / 0 | |
| 0.0.6 | 2 / 0 | |
| 0.0.5 | 2 / 0 | |
| 0.0.4 | 2 / 0 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 2 / 0 |
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.