serverless
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:xml2js | AI (phantom-deps): xml2js is a declared runtime dependency; phantom-dep heuristic misfires for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Established Serverless Framework CLI; postinstall is a documented setup step, stable across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in binary.js for CLI tooling; expected pattern for this package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 4.36.1 | 2 / 0 | |
| 4.35.1 | 2 / 0 | |
| 4.35.0 | 2 / 0 | |
| 4.32.0 | 4 / 0 | |
| 4.31.1 | 4 / 0 | |
| 4.31.0 | 4 / 5 | |
| 4.27.0 | 4 / 5 | |
| 4.26.1 | 4 / 5 | |
| 4.14.3 | 4 / 5 | |
| 4.4.5 | 4 / 5 | |
| 4.4.4 | 4 / 5 | |
| 4.4.3 | 4 / 5 | |
| 4.4.2 | 4 / 5 | |
| 4.4.1 | 4 / 5 | |
| 4.4.0 | 4 / 5 | |
| 4.3.3 | 4 / 5 | |
| 4.3.2 | 4 / 5 | |
| 4.3.1 | 4 / 5 | |
| 4.3.0 | 4 / 5 | |
| 4.2.5 | 4 / 5 | |
| 4.2.4 | 4 / 5 | |
| 4.2.3 | 4 / 5 | |
| 4.2.1 | 4 / 5 | |
| 4.2.0 | 4 / 5 | |
| 4.1.24 | 4 / 5 | |
| 4.1.23 | 4 / 5 | |
| 4.1.22 | 4 / 5 | |
| 4.1.21 | 3 / 5 | |
| 4.1.20 | 3 / 5 | |
| 4.1.19 | 3 / 5 | |
| 4.1.18 | 3 / 5 | |
| 4.1.17 | 3 / 5 | |
| 4.1.15 | 3 / 5 | |
| 4.1.12 | 3 / 5 | |
| 4.1.11 | 3 / 5 | |
| 4.1.10 | 3 / 5 | |
| 4.1.9 | 3 / 5 | |
| 4.1.7 | 3 / 5 | |
| 4.1.6 | 3 / 5 | |
| 4.1.5 | 3 / 5 | |
| 4.1.0 | 3 / 5 | |
| 4.0.35 | 3 / 5 | |
| 4.0.24 | 3 / 5 | |
| 4.0.23 | 3 / 5 | |
| 4.0.22 | 3 / 5 | |
| 4.0.0 | 3 / 5 |
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.