@steedos/plugin-keycloak
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
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.5.52 | 0 / 8 | |
| 2.5.51 | 0 / 8 | |
| 2.5.50 | 0 / 8 | |
| 2.5.49 | 0 / 8 |
v2.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.51
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-baozhoutao) than the most recent previously approved version (steedos-sunhaolin) on 2025-07-05, but steedos-baozhoutao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.5.50
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steedos-sunhaolin) than the most recent previously approved version (chenzhipei) on 2025-04-18, but steedos-sunhaolin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.5.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.