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 9 of 9)
| 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 |
v4.36.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.35.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.35.0
2 findingsScript: node ./postInstall.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.31.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.