@kne/info-page
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kne/is-empty | AI (dependencies): Same @kne org scope as this package; consistent with publisher's ecosystem pattern. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.2.10 | 4 / 9 | |
| 0.2.9 | 4 / 9 | |
| 0.2.8 | 4 / 9 | |
| 0.2.7 | 4 / 9 | |
| 0.2.6 | 4 / 9 | |
| 0.2.5 | 4 / 9 | |
| 0.2.4 | 4 / 9 | |
| 0.2.3 | 4 / 9 | |
| 0.2.2 | 4 / 9 | |
| 0.2.1 | 4 / 9 | |
| 0.2.0 | 4 / 9 | |
| 0.1.29 | 4 / 9 | |
| 0.1.28 | 4 / 9 | |
| 0.1.27 | 4 / 9 | |
| 0.1.26 | 4 / 9 | |
| 0.1.25 | 4 / 9 | |
| 0.1.24 | 4 / 9 | |
| 0.1.23 | 4 / 9 | |
| 0.1.22 | 4 / 9 | |
| 0.1.21 | 4 / 9 | |
| 0.1.20 | 4 / 9 | |
| 0.1.19 | 4 / 9 | |
| 0.1.18 | 4 / 9 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.