@edifice.io/edifice-ent-client
Clients to interact with ent-nats-service
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
Versions (showing 19 of 123)
| Version | Deps | Published |
|---|---|---|
| 6.10.1762935270103 | 0 / 9 | |
| 6.10.1762789334121 | 0 / 9 | |
| 6.10.5 | 0 / 9 | |
| 6.10.4 | 0 / 9 | |
| 6.10.3 | 0 / 9 | |
| 6.10.2 | 0 / 9 | |
| 6.10.1 | 0 / 9 | |
| 6.10.0 | 0 / 9 | |
| 6.9.1762432399921 | 0 / 9 | |
| 6.9.1762352912104 | 0 / 9 | |
| 6.9.6 | 0 / 9 | |
| 6.9.5 | 0 / 9 | |
| 6.9.4 | 0 / 9 | |
| 6.9.3 | 0 / 9 | |
| 6.9.2 | 0 / 9 | |
| 6.9.1 | 0 / 9 | |
| 6.9.0 | 0 / 9 | |
| 1.0.1780072189643 | 0 / 9 | |
| 1.0.0 | 0 / 9 |
v6.10.1762935270103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1762789334121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1762432399921
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1762352912104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1780072189643
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.