@3mo/fetchable-data-grid
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 9 / 0 | |
| 0.5.1 | 9 / 0 | |
| 0.5.0 | 9 / 0 | |
| 0.4.2 | 8 / 0 | |
| 0.4.1 | 8 / 0 | |
| 0.4.0 | 8 / 0 | |
| 0.3.0 | 8 / 0 | |
| 0.2.5 | 8 / 0 | |
| 0.2.4 | 8 / 0 | |
| 0.2.3 | 8 / 0 | |
| 0.2.2 | 8 / 0 | |
| 0.2.1 | 8 / 0 | |
| 0.2.0 | 8 / 0 | |
| 0.1.4 | 8 / 0 | |
| 0.1.3 | 8 / 0 | |
| 0.1.2 | 8 / 0 | |
| 0.1.1 | 8 / 0 | |
| 0.1.0 | 8 / 0 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.