@golemio/ndic
Golemio NDIC Module
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
Keywords
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 2 / 40 | |
| 1.8.0 | 1 / 39 | |
| 1.7.0 | 1 / 39 | |
| 1.6.8 | 1 / 39 | |
| 1.6.7 | 1 / 39 | |
| 1.6.6 | 1 / 39 | |
| 1.6.5 | 1 / 39 | |
| 1.6.4 | 1 / 39 | |
| 1.6.3 | 1 / 39 | |
| 1.6.2 | 1 / 39 | |
| 1.6.1 | 1 / 39 | |
| 1.6.0 | 1 / 39 | |
| 1.5.0 | 1 / 39 | |
| 1.4.2 | 1 / 39 | |
| 1.4.1 | 1 / 39 | |
| 1.4.0 | 1 / 39 | |
| 1.3.1 | 1 / 39 | |
| 1.3.0 | 1 / 39 | |
| 1.2.9 | 0 / 38 | |
| 1.2.8 | 0 / 38 | |
| 1.2.7 | 0 / 38 |
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.