@steedos/service-ancillary
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher is part of the same steedos org with a clean track record (195/0); consistent with internal maintainer rotation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org service package; sparse metadata is consistent across all @steedos/* packages. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dependency; phantom-dep heuristic fires but it's legitimately used. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.7.32 | 4 / 0 | |
| 2.7.31 | 4 / 0 | |
| 2.7.30 | 4 / 0 | |
| 2.7.29 | 4 / 0 | |
| 2.7.28 | 4 / 0 | |
| 2.7.27 | 4 / 0 | |
| 2.7.25 | 4 / 0 | |
| 2.7.24 | 4 / 0 | |
| 2.7.23 | 4 / 0 | |
| 2.7.22 | 4 / 0 | |
| 2.7.21 | 4 / 0 | |
| 2.7.20 | 4 / 0 | |
| 2.7.19 | 4 / 0 | |
| 2.7.18 | 4 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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.23
2 findingsThis version was published by a different npm account than previous versions on 2025-11-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.