@steedos/service-charts
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Worker class-loader pattern; resolves user-supplied module/classname at runtime by design, stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package in large Steedos monorepo; sparse README is a documentation issue, not a spam indicator. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.7.32 | 5 / 8 | |
| 2.7.31 | 5 / 8 | |
| 2.7.30 | 5 / 8 | |
| 2.7.29 | 5 / 8 | |
| 2.7.28 | 5 / 8 | |
| 2.7.27 | 5 / 8 | |
| 2.7.25 | 5 / 8 | |
| 2.7.24 | 5 / 8 |
v2.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.