@stackpress/ingest
An unopinionated, event driven, pluggable, server/less framework
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:dynamic-require | AI (semgrep): Dynamic import is used in Loader.js to load user-specified route/plugin files by path — core framework functionality, not a security risk. | ai |
Versions (showing 100 of 110)
| Version | Deps | Published |
|---|---|---|
| 0.10.8 | 2 / 9 | |
| 0.10.7 | 2 / 9 | |
| 0.10.6 | 2 / 9 | |
| 0.10.5 | 2 / 9 | |
| 0.10.4 | 2 / 9 | |
| 0.10.3 | 2 / 9 | |
| 0.10.1 | 2 / 9 | |
| 0.9.2 | 2 / 9 | |
| 0.9.1 | 2 / 9 | |
| 0.8.3 | 2 / 9 | |
| 0.8.2 | 2 / 9 | |
| 0.8.1 | 2 / 9 | |
| 0.7.2 | 2 / 9 | |
| 0.7.1 | 2 / 9 | |
| 0.6.14 | 2 / 9 | |
| 0.6.12 | 2 / 9 | |
| 0.6.11 | 2 / 9 | |
| 0.6.10 | 2 / 9 | |
| 0.6.9 | 2 / 9 | |
| 0.6.8 | 2 / 9 | |
| 0.6.7 | 2 / 9 | |
| 0.6.6 | 2 / 9 | |
| 0.6.5 | 2 / 9 | |
| 0.6.4 | 2 / 9 | |
| 0.6.3 | 2 / 9 | |
| 0.6.2 | 2 / 9 | |
| 0.6.1 | 2 / 9 | |
| 0.5.30 | 2 / 9 | |
| 0.5.29 | 2 / 9 | |
| 0.5.28 | 2 / 9 | |
| 0.5.27 | 2 / 9 | |
| 0.5.26 | 2 / 9 | |
| 0.5.25 | 2 / 9 | |
| 0.5.24 | 2 / 9 | |
| 0.5.23 | 2 / 9 | |
| 0.5.22 | 2 / 9 | |
| 0.5.19 | 2 / 9 | |
| 0.5.17 | 2 / 9 | |
| 0.5.16 | 2 / 9 | |
| 0.5.15 | 2 / 9 | |
| 0.5.14 | 2 / 9 | |
| 0.5.12 | 2 / 9 | |
| 0.5.11 | 2 / 9 | |
| 0.5.10 | 3 / 9 | |
| 0.5.9 | 3 / 9 | |
| 0.5.8 | 3 / 9 | |
| 0.5.7 | 3 / 9 | |
| 0.5.6 | 3 / 9 | |
| 0.5.5 | 3 / 9 | |
| 0.5.4 | 3 / 9 | |
| 0.5.2 | 3 / 9 | |
| 0.4.6 | 3 / 8 | |
| 0.4.5 | 3 / 8 | |
| 0.4.4 | 3 / 8 | |
| 0.4.3 | 3 / 8 | |
| 0.4.2 | 3 / 8 | |
| 0.4.1 | 3 / 8 | |
| 0.3.36 | 3 / 8 | |
| 0.3.34 | 3 / 8 | |
| 0.3.33 | 3 / 8 | |
| 0.3.32 | 3 / 8 | |
| 0.3.31 | 3 / 8 | |
| 0.3.30 | 3 / 8 | |
| 0.3.29 | 3 / 8 | |
| 0.3.28 | 3 / 8 | |
| 0.3.27 | 3 / 8 | |
| 0.3.26 | 3 / 8 | |
| 0.3.25 | 3 / 8 | |
| 0.3.24 | 3 / 8 | |
| 0.3.23 | 3 / 8 | |
| 0.3.21 | 3 / 8 | |
| 0.3.17 | 3 / 9 | |
| 0.3.16 | 3 / 9 | |
| 0.3.15 | 3 / 9 | |
| 0.3.11 | 3 / 9 | |
| 0.3.10 | 3 / 9 | |
| 0.3.9 | 3 / 9 | |
| 0.3.8 | 3 / 9 | |
| 0.3.7 | 3 / 9 | |
| 0.3.6 | 3 / 9 | |
| 0.2.14 | 4 / 9 | |
| 0.2.12 | 4 / 9 | |
| 0.2.11 | 4 / 9 | |
| 0.2.10 | 4 / 9 | |
| 0.2.7 | 4 / 9 | |
| 0.2.6 | 4 / 9 | |
| 0.2.5 | 4 / 9 | |
| 0.2.3 | 4 / 9 | |
| 0.1.26 | 3 / 12 | |
| 0.1.25 | 2 / 13 | |
| 0.1.23 | 2 / 6 | |
| 0.1.22 | 2 / 6 | |
| 0.1.21 | 2 / 6 | |
| 0.1.17 | 2 / 6 | |
| 0.1.16 | 2 / 6 | |
| 0.1.15 | 2 / 6 | |
| 0.1.14 | 2 / 6 | |
| 0.1.12 | 2 / 6 | |
| 0.1.11 | 2 / 6 | |
| 0.1.10 | 2 / 6 |
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.