@steedos/print-template
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64 image data constant in bundled build, not an obfuscated payload. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Known maintainer, long-lived low-traffic internal package; no malicious behavior found. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is first-party @steedos/utils sibling package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.5.52 | 4 / 3 | |
| 2.5.51 | 4 / 3 | |
| 2.5.50 | 4 / 3 | |
| 2.5.49 | 3 / 3 |
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
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package 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 (chenzhipei) 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
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package 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.