@onesy/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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:fe | AI (dependencies): fe is a legitimate small utility lib, not malicious or unresolvable. | ai | |
| phantom-deps | phantom-dep:fe | AI (phantom-deps): Likely used indirectly/build-time; not a security concern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Package is a utils library with explicit encode/decode functions; base64 decoding is core functionality, not obfuscation. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() used only for environment detection (nodejs/browser check) with a hardcoded string — not user-controlled input. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard Babel transpilation helper; loaded by convention in transpiled output. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.0.20 | 5 / 0 | |
| 1.0.19 | 5 / 0 | |
| 1.0.18 | 5 / 0 | |
| 1.0.17 | 5 / 0 | |
| 1.0.16 | 5 / 0 | |
| 1.0.15 | 5 / 0 | |
| 1.0.14 | 5 / 0 | |
| 1.0.13 | 5 / 0 | |
| 1.0.12 | 5 / 0 | |
| 1.0.11 | 5 / 0 | |
| 1.0.10 | 5 / 0 | |
| 1.0.7 | 4 / 0 | |
| 1.0.5 | 4 / 0 | |
| 1.0.4 | 4 / 0 | |
| 1.0.3 | 4 / 0 | |
| 1.0.2 | 4 / 0 | |
| 1.0.1 | 4 / 0 | |
| 1.0.0 | 4 / 0 |
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.