@adobe/edgly
Command line tool to boost Fastly VCL service development
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:tiny-update-notifier | AI (dependencies): tiny-update-notifier is a benign update-notifier utility; stable false positive for this CLI package. | ai | |
| provenance | no-provenance | AI (provenance): Adobe org package; missing provenance is common and not a risk signal here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.4.5 | 7 / 12 | |
| 1.4.4 | 7 / 12 | |
| 1.4.3 | 7 / 12 | |
| 1.4.2 | 7 / 12 | |
| 1.4.1 | 7 / 12 | |
| 1.4.0 | 7 / 12 | |
| 1.3.11 | 7 / 12 | |
| 1.3.10 | 7 / 12 | |
| 1.3.9 | 7 / 12 | |
| 1.3.8 | 7 / 12 | |
| 1.3.7 | 7 / 12 | |
| 1.3.6 | 7 / 12 | |
| 1.3.5 | 7 / 12 | |
| 1.3.4 | 7 / 12 |
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.