@yamf/services-deploy-router MIT 2 versions

@yamf/services-deploy-router

npm Repository Homepage

Registry plugin: deploy-plan + deploy-bundle (slice C3)

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yamf

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Common for small org packages; no other risk signals present.	ai	2026/05/14

Versions (showing 2 of 2)

Version	Deps	Published
0.9.0	1 / 1	2026-05-17
0.1.0	1 / 1	2026-04-28

v0.9.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.