@steedos/service-package-loader
<!-- * @Author: 孙浩林 [email protected] * @Date: 2021-10-21 14:19:05 * @LastEditors: 孙浩林 [email protected] * @LastEditTime: 2023-10-27 13:00:22 * @FilePath: /steedos-platform-2.3/services/service-package-loader/README.md * @Description: --> #
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-xlsx | AI (dependencies): node-xlsx is a well-known Excel parsing library; stable dependency across many versions of this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json from a known package path — standard loader pattern, not arbitrary module loading. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @steedos scoped package; sparse metadata is consistent across the org's 1400+ versions. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used solely to parse user-supplied regex literals (strings starting with '/'); not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:clone | AI (phantom-deps): clone is declared in dependencies in package.json; phantom-dep heuristic false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.12 | 10 / 1 | |
| 3.0.4 | 10 / 1 | |
| 3.0.3 | 10 / 1 | |
| 2.7.32 | 10 / 1 | |
| 2.7.30 | 10 / 1 | |
| 2.7.25 | 10 / 1 | |
| 2.7.24 | 10 / 1 | |
| 2.7.23 | 10 / 1 |
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.