@daysnap/utils
通用的工具库
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 133)
| Version | Deps | Published |
|---|---|---|
| 0.1.36 | 0 / 22 | |
| 0.1.35 | 0 / 22 | |
| 0.1.34 | 0 / 22 | |
| 0.1.33 | 0 / 22 | |
| 0.1.32 | 0 / 22 | |
| 0.1.31 | 0 / 22 | |
| 0.1.30 | 0 / 22 | |
| 0.1.29 | 0 / 22 | |
| 0.1.28 | 0 / 22 | |
| 0.1.27 | 0 / 22 | |
| 0.1.26 | 0 / 22 | |
| 0.1.25 | 0 / 22 | |
| 0.1.24 | 0 / 22 | |
| 0.1.23 | 0 / 22 | |
| 0.1.22 | 0 / 22 | |
| 0.1.21 | 0 / 22 | |
| 0.1.17 | 0 / 22 | |
| 0.1.16 | 0 / 22 | |
| 0.1.15 | 0 / 22 | |
| 0.1.14 | 0 / 22 | |
| 0.1.13 | 0 / 22 | |
| 0.1.12 | 0 / 22 | |
| 0.1.11 | 0 / 22 | |
| 0.1.10 | 0 / 22 | |
| 0.1.9 | 0 / 22 | |
| 0.1.8 | 0 / 22 | |
| 0.1.7 | 0 / 22 | |
| 0.1.6 | 0 / 22 | |
| 0.1.5 | 0 / 22 | |
| 0.1.4 | 0 / 22 | |
| 0.1.3 | 0 / 22 | |
| 0.1.2 | 0 / 22 | |
| 0.1.1 | 0 / 22 | |
| 0.1.0 | 0 / 22 | |
| 0.0.99 | 0 / 22 | |
| 0.0.98 | 0 / 22 | |
| 0.0.97 | 0 / 22 | |
| 0.0.96 | 0 / 22 | |
| 0.0.95 | 0 / 22 | |
| 0.0.94 | 0 / 22 | |
| 0.0.93 | 0 / 21 | |
| 0.0.92 | 0 / 21 | |
| 0.0.91 | 0 / 21 | |
| 0.0.90 | 0 / 21 | |
| 0.0.89 | 0 / 21 | |
| 0.0.88 | 0 / 21 | |
| 0.0.87 | 0 / 21 | |
| 0.0.86 | 0 / 21 | |
| 0.0.85 | 0 / 21 | |
| 0.0.84 | 0 / 21 | |
| 0.0.83 | 0 / 21 | |
| 0.0.82 | 0 / 21 | |
| 0.0.81 | 0 / 21 | |
| 0.0.80 | 0 / 21 | |
| 0.0.79 | 0 / 21 | |
| 0.0.78 | 0 / 21 | |
| 0.0.77 | 0 / 21 | |
| 0.0.76 | 0 / 21 | |
| 0.0.75 | 0 / 21 | |
| 0.0.74 | 0 / 21 | |
| 0.0.73 | 0 / 21 | |
| 0.0.72 | 0 / 21 | |
| 0.0.71 | 0 / 21 | |
| 0.0.70 | 0 / 21 | |
| 0.0.69 | 0 / 21 | |
| 0.0.68 | 0 / 21 | |
| 0.0.67 | 0 / 20 | |
| 0.0.66 | 0 / 20 | |
| 0.0.65 | 0 / 20 | |
| 0.0.64 | 0 / 20 | |
| 0.0.63 | 0 / 20 | |
| 0.0.62 | 0 / 20 | |
| 0.0.61 | 0 / 20 | |
| 0.0.60 | 0 / 20 | |
| 0.0.59 | 0 / 20 | |
| 0.0.58 | 0 / 20 | |
| 0.0.57 | 0 / 20 | |
| 0.0.56 | 0 / 20 | |
| 0.0.55 | 0 / 20 | |
| 0.0.54 | 0 / 20 | |
| 0.0.53 | 0 / 20 | |
| 0.0.52 | 0 / 20 | |
| 0.0.51 | 0 / 20 | |
| 0.0.50 | 0 / 20 | |
| 0.0.49 | 0 / 20 | |
| 0.0.48 | 0 / 20 | |
| 0.0.47 | 0 / 20 | |
| 0.0.46 | 0 / 20 | |
| 0.0.45 | 0 / 20 | |
| 0.0.44 | 0 / 20 | |
| 0.0.43 | 0 / 20 | |
| 0.0.42 | 0 / 20 | |
| 0.0.41 | 1 / 23 | |
| 0.0.40 | 1 / 23 | |
| 0.0.39 | 1 / 23 | |
| 0.0.38 | 1 / 23 | |
| 0.0.37 | 1 / 23 | |
| 0.0.36 | 1 / 23 | |
| 0.0.35 | 1 / 23 | |
| 0.0.34 | 1 / 23 |
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dafudagui) than the most recent previously approved version (woshiajuana) on 2024-06-11, but dafudagui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (woshiajuana) than the most recent previously approved version (dafudagui) on 2023-12-31, but woshiajuana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.80
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (woshiajuana) than the most recent previously approved version (dafudagui) on 2023-12-31, but woshiajuana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dafudagui) than the most recent previously approved version (woshiajuana) on 2023-12-18, but dafudagui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (woshiajuana) than the most recent previously approved version (dafudagui) on 2023-11-22, but woshiajuana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dafudagui) than the most recent previously approved version (woshiajuana) on 2023-11-22, but dafudagui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (woshiajuana) than the most recent previously approved version (dafudagui) on 2023-08-04, but woshiajuana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.57
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (woshiajuana) than the most recent previously approved version (dafudagui) on 2023-08-03, but woshiajuana is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.56
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dafudagui) than the most recent previously approved version (woshiajuana) on 2023-08-02, but dafudagui is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.