@steedos/service-enterprise
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:dynamic-require | AI (semgrep): Plugin-loader pattern in package.service.js; stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:mssql | AI (phantom-deps): Optional DB driver declared for config-driven loading, not direct import; stable for this package. | ai | |
| phantom-deps | phantom-dep:oracledb | AI (phantom-deps): Optional DB driver declared for config-driven loading, not direct import; stable for this package. | ai | |
| phantom-deps | phantom-dep:@steedos/ee_branding | AI (phantom-deps): Same-org package loaded via plugin mechanism, not direct import; stable for this package. | ai | |
| phantom-deps | phantom-dep:@steedos-labs/analytics | AI (phantom-deps): Config-driven plugin loading pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@steedos/service-license | AI (phantom-deps): Same-org package loaded via plugin mechanism; stable for this package. | ai | |
| phantom-deps | phantom-dep:@steedos-labs/plugin-workflow | AI (phantom-deps): Config-driven plugin loading pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@steedos-labs/plugin-print-template | AI (phantom-deps): Config-driven plugin loading pattern; stable for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.14 | 7 / 0 | |
| 3.0.13 | 7 / 0 | |
| 3.0.12 | 7 / 0 | |
| 3.0.11 | 7 / 0 | |
| 3.0.10 | 7 / 0 | |
| 3.0.9 | 7 / 0 | |
| 3.0.8 | 7 / 0 | |
| 3.0.7 | 7 / 0 | |
| 3.0.6 | 7 / 0 | |
| 3.0.4 | 7 / 0 | |
| 3.0.3 | 7 / 0 | |
| 3.0.2 | 7 / 0 | |
| 3.0.1 | 7 / 0 |
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.