@oscarpalmer/atoms
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 100 of 222)
| Version | Deps | Published |
|---|---|---|
| 0.112.0 | 1 / 11 | |
| 0.111.1 | 1 / 11 | |
| 0.111.0 | 1 / 11 | |
| 0.110.2 | 1 / 11 | |
| 0.110.1 | 1 / 11 | |
| 0.110.0 | 1 / 11 | |
| 0.109.0 | 1 / 13 | |
| 0.108.0 | 1 / 13 | |
| 0.107.0 | 1 / 13 | |
| 0.106.0 | 1 / 12 | |
| 0.105.1 | 1 / 12 | |
| 0.105.0 | 1 / 12 | |
| 0.104.0 | 1 / 12 | |
| 0.103.0 | 1 / 12 | |
| 0.102.0 | 1 / 12 | |
| 0.101.0 | 1 / 12 | |
| 0.100.0 | 1 / 12 | |
| 0.99.0 | 1 / 13 | |
| 0.98.0 | 1 / 12 | |
| 0.97.0 | 1 / 9 | |
| 0.96.0 | 1 / 9 | |
| 0.95.0 | 1 / 9 | |
| 0.94.0 | 1 / 9 | |
| 0.93.0 | 1 / 9 | |
| 0.92.0 | 1 / 9 | |
| 0.91.0 | 1 / 9 | |
| 0.90.0 | 1 / 9 | |
| 0.89.1 | 1 / 9 | |
| 0.89.0 | 1 / 9 | |
| 0.87.0 | 1 / 9 | |
| 0.86.1 | 1 / 9 | |
| 0.86.0 | 1 / 9 | |
| 0.85.0 | 1 / 9 | |
| 0.84.0 | 1 / 9 | |
| 0.83.0 | 1 / 9 | |
| 0.82.1 | 1 / 9 | |
| 0.82.0 | 1 / 9 | |
| 0.81.0 | 1 / 9 | |
| 0.80.0 | 1 / 9 | |
| 0.79.0 | 1 / 9 | |
| 0.78.0 | 1 / 9 | |
| 0.77.3 | 1 / 10 | |
| 0.77.2 | 1 / 10 | |
| 0.77.1 | 1 / 10 | |
| 0.77.0 | 1 / 10 | |
| 0.76.0 | 1 / 10 | |
| 0.75.0 | 1 / 9 | |
| 0.74.1 | 1 / 8 | |
| 0.74.0 | 1 / 8 | |
| 0.73.0 | 1 / 8 | |
| 0.72.0 | 1 / 8 | |
| 0.71.0 | 1 / 8 | |
| 0.70.1 | 2 / 7 | |
| 0.70.0 | 2 / 7 | |
| 0.69.0 | 1 / 7 | |
| 0.68.1 | 1 / 7 | |
| 0.68.0 | 1 / 7 | |
| 0.67.0 | 1 / 7 | |
| 0.66.0 | 1 / 7 | |
| 0.65.0 | 1 / 7 | |
| 0.64.0 | 1 / 7 | |
| 0.63.0 | 1 / 7 | |
| 0.62.0 | 1 / 7 | |
| 0.61.0 | 1 / 7 | |
| 0.60.0 | 1 / 7 | |
| 0.59.0 | 1 / 7 | |
| 0.58.0 | 1 / 6 | |
| 0.57.0 | 1 / 6 | |
| 0.56.1 | 1 / 6 | |
| 0.56.0 | 1 / 6 | |
| 0.55.0 | 1 / 6 | |
| 0.54.0 | 1 / 6 | |
| 0.53.0 | 1 / 6 | |
| 0.52.0 | 1 / 6 | |
| 0.51.0 | 1 / 6 | |
| 0.50.0 | 1 / 6 | |
| 0.49.0 | 1 / 5 | |
| 0.48.0 | 1 / 5 | |
| 0.47.1 | 1 / 5 | |
| 0.47.0 | 1 / 5 | |
| 0.46.0 | 1 / 5 | |
| 0.45.0 | 1 / 5 | |
| 0.44.0 | 1 / 5 | |
| 0.43.0 | 1 / 5 | |
| 0.42.0 | 1 / 5 | |
| 0.41.4 | 1 / 5 | |
| 0.41.3 | 1 / 5 | |
| 0.41.2 | 1 / 5 | |
| 0.41.1 | 1 / 5 | |
| 0.41.0 | 1 / 5 | |
| 0.40.0 | 1 / 5 | |
| 0.39.0 | 1 / 5 | |
| 0.38.1 | 1 / 5 | |
| 0.38.0 | 1 / 5 | |
| 0.37.0 | 1 / 5 | |
| 0.36.0 | 1 / 5 | |
| 0.35.0 | 1 / 5 | |
| 0.34.0 | 1 / 5 | |
| 0.33.0 | 1 / 5 | |
| 0.32.0 | 0 / 5 |
v0.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.86.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.74.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.