@entur/function-tools
Ekstra verktøy for firebase 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): CLI tool that spawns subprocesses; spreading process.env to child process options is standard and intentional. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-dts | AI (phantom-deps): rollup-plugin-dts is a declared runtime dep used in rollup config files, not directly imported — stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.16 | 10 / 0 | |
| 0.0.15 | 10 / 0 | |
| 0.0.14 | 10 / 0 | |
| 0.0.13 | 10 / 0 | |
| 0.0.12 | 10 / 0 | |
| 0.0.11 | 10 / 0 | |
| 0.0.10 | 10 / 0 | |
| 0.0.9 | 10 / 0 | |
| 0.0.8 | 10 / 0 | |
| 0.0.7 | 10 / 0 | |
| 0.0.6 | 10 / 0 | |
| 0.0.5 | 11 / 0 | |
| 0.0.4 | 11 / 0 | |
| 0.0.3 | 11 / 0 | |
| 0.0.2 | 11 / 0 | |
| 0.0.1 | 11 / 0 |
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
3 findingsSpreading entire process.env into an object — may capture all secrets 19 | ], { 20 | cwd, > 21 | env: { 22 | ...process.env, 23 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 46 | ], { 47 | cwd, > 48 | env: { 49 | ...process.env, 50 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
3 findingsSpreading entire process.env into an object — may capture all secrets 17 | ], { 18 | cwd, > 19 | env: { 20 | ...process.env, 21 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 44 | ], { 45 | cwd, > 46 | env: { 47 | ...process.env, 48 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
3 findingsSpreading entire process.env into an object — may capture all secrets 11 | ], { 12 | cwd, > 13 | env: { 14 | ...process.env, 15 | FUNCTIONS_DISCOVERY_TIMEOUT
Spreading entire process.env into an object — may capture all secrets 38 | ], { 39 | cwd, > 40 | env: { 41 | ...process.env, 42 | FUNCTIONS_DISCOVERY_TIMEOUT
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
2 findingsSpreading entire process.env into an object — may capture all secrets 89 | ], { 90 | cwd: workingDir, > 91 | env: { 92 | ...process.env, 93 | FUNCTION_CODEBASE: codebase,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
2 findingsSpreading entire process.env into an object — may capture all secrets 79 | ], { 80 | cwd: workingDir, > 81 | env: { 82 | ...process.env, 83 | FUNCTION_CODEBASE: codebase,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findingsSpreading entire process.env into an object — may capture all secrets 79 | ], { 80 | cwd: workingDir, > 81 | env: { 82 | ...process.env, 83 | FUNCTION_CODEBASE: codebase,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsSpreading entire process.env into an object — may capture all secrets 79 | ], { 80 | cwd: workingDir, > 81 | env: { 82 | ...process.env, 83 | FUNCTION_CODEBASE: codebase,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsSpreading entire process.env into an object — may capture all secrets 79 | ], { 80 | cwd: workingDir, > 81 | env: { 82 | ...process.env, 83 | FUNCTION_CODEBASE: codebase,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.