runed
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Legit dep likely used internally; no malicious behavior, common false positive for early versions. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Placeholder initial publish for a package now at v0.37.1 with heavy adoption; not throwaway. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty metadata on initial 0.0.0 reservation publish, filled in later versions. | ai | |
| provenance | publisher-changed | AI (provenance): Project uses GitHub Actions for publishing with SLSA provenance; 'huntabyte → GitHub Actions' is an expected CI migration, not a takeover. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes with SLSA provenance via GitHub Actions CI/CD. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.37.1 | 3 / 24 | |
| 0.37.0 | 3 / 24 | |
| 0.36.0 | 3 / 24 | |
| 0.35.1 | 3 / 23 | |
| 0.35.0 | 3 / 23 | |
| 0.34.0 | 3 / 23 | |
| 0.33.0 | 3 / 23 | |
| 0.32.0 | 3 / 23 | |
| 0.31.1 | 1 / 22 | |
| 0.31.0 | 1 / 22 | |
| 0.30.0 | 1 / 22 | |
| 0.29.2 | 1 / 22 | |
| 0.29.1 | 1 / 22 | |
| 0.29.0 | 1 / 22 | |
| 0.28.0 | 1 / 22 | |
| 0.27.0 | 1 / 20 | |
| 0.26.0 | 1 / 20 | |
| 0.25.0 | 1 / 20 | |
| 0.24.1 | 1 / 20 | |
| 0.24.0 | 1 / 20 | |
| 0.23.4 | 1 / 19 | |
| 0.23.3 | 1 / 19 | |
| 0.23.2 | 1 / 19 | |
| 0.23.1 | 1 / 19 | |
| 0.23.0 | 1 / 19 | |
| 0.22.0 | 1 / 19 | |
| 0.21.0 | 1 / 19 | |
| 0.20.0 | 1 / 19 | |
| 0.19.0 | 1 / 19 | |
| 0.18.0 | 1 / 19 | |
| 0.17.0 | 1 / 19 | |
| 0.16.3 | 1 / 19 | |
| 0.16.2 | 1 / 19 | |
| 0.16.1 | 1 / 19 | |
| 0.16.0 | 1 / 19 | |
| 0.15.4 | 1 / 19 | |
| 0.15.3 | 1 / 19 | |
| 0.15.2 | 1 / 19 | |
| 0.15.1 | 1 / 19 | |
| 0.15.0 | 1 / 19 | |
| 0.14.0 | 1 / 19 | |
| 0.13.0 | 2 / 14 | |
| 0.12.1 | 2 / 13 | |
| 0.12.0 | 2 / 13 | |
| 0.10.0 | 1 / 13 | |
| 0.9.1 | 1 / 13 | |
| 0.9.0 | 1 / 13 | |
| 0.7.0 | 1 / 13 | |
| 0.6.0 | 1 / 13 | |
| 0.5.0 | 1 / 13 | |
| 0.4.1 | 1 / 13 | |
| 0.4.0 | 1 / 13 | |
| 0.3.0 | 1 / 14 | |
| 0.2.0 | 1 / 14 | |
| 0.1.0 | 1 / 14 | |
| 0.0.0 | 0 / 0 |
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.