@steedos/service-package-tool
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes a URL query param for API input; guarded by admin permission check immediately after. Not a payload-hiding pattern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:jsonata | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:radwag-mass | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:package-json | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@steedos/auth | AI (phantom-deps): Same org scope; declared dependency used transitively in monorepo context. | ai | |
| phantom-deps | phantom-dep:moment-timezone | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:npm-package-arg | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:json-stringify-safe | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:npm-registry-client | AI (phantom-deps): Declared in package.json, referenced in config files; monorepo tool pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@steedos/metadata-core | AI (phantom-deps): Same org scope; declared dependency used transitively in monorepo context. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.7.32 | 17 / 0 | |
| 2.7.31 | 17 / 0 | |
| 2.7.30 | 17 / 0 | |
| 2.7.29 | 17 / 0 | |
| 2.7.28 | 17 / 0 | |
| 2.7.27 | 17 / 0 | |
| 2.7.25 | 17 / 0 | |
| 2.7.24 | 17 / 0 | |
| 2.7.22 | 17 / 0 | |
| 2.7.21 | 17 / 0 | |
| 2.7.20 | 17 / 0 | |
| 2.7.19 | 17 / 0 | |
| 2.7.18 | 17 / 0 |
v2.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.27
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.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.