@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 51 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 |
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.