@tenancy.nz/icons
Icon library for TPS UI.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped icon library for tenancy.nz; Levenshtein match to 'cors' is coincidental and not a squatting attempt. | ai | |
| email-domain | unclaimed-email:https://www.tenancy.co.nz | AI (email-domain): Author field uses a URL string as email value, not a real email address; not an actual domain-hijack risk. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 0 / 0 | |
| 1.7.3 | 0 / 0 | |
| 1.7.2 | 0 / 0 | |
| 1.7.1 | 0 / 0 | |
| 1.7.0 | 0 / 0 | |
| 1.6.7 | 0 / 0 | |
| 1.6.6 | 0 / 0 | |
| 1.6.5 | 0 / 0 | |
| 1.6.4 | 0 / 0 | |
| 1.6.3 | 0 / 0 | |
| 1.6.2 | 0 / 0 | |
| 1.6.1 | 0 / 0 | |
| 1.6.0 | 0 / 0 | |
| 1.5.9 | 0 / 0 | |
| 1.5.8 | 0 / 0 | |
| 1.5.7 | 0 / 0 | |
| 1.5.6 | 0 / 0 | |
| 1.5.5 | 0 / 0 | |
| 1.5.4 | 0 / 0 | |
| 1.5.3 | 0 / 0 | |
| 1.5.2 | 0 / 0 | |
| 1.5.1 | 0 / 0 | |
| 1.5.0 | 0 / 0 | |
| 1.4.11 | 0 / 0 | |
| 1.4.10 | 0 / 0 | |
| 1.4.9 | 0 / 0 | |
| 1.4.8 | 0 / 0 | |
| 1.4.7 | 0 / 0 | |
| 1.4.6 | 0 / 0 | |
| 1.4.5 | 0 / 0 | |
| 1.4.4 | 0 / 0 | |
| 1.4.3 | 0 / 0 | |
| 1.4.2 | 0 / 0 | |
| 1.4.1 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.10 | 0 / 0 | |
| 1.3.9 | 0 / 0 | |
| 1.3.8 | 0 / 0 | |
| 1.3.7 | 0 / 0 | |
| 1.3.6 | 0 / 0 | |
| 1.3.4 | 0 / 1 | |
| 1.3.3 | 0 / 1 | |
| 1.3.2 | 0 / 1 | |
| 1.3.1 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.14 | 0 / 1 | |
| 1.2.12 | 0 / 1 | |
| 1.2.11 | 0 / 1 | |
| 1.2.10 | 0 / 1 | |
| 1.2.9 | 0 / 1 | |
| 1.2.8 | 0 / 1 | |
| 1.2.7 | 0 / 1 | |
| 1.2.6 | 0 / 1 | |
| 1.2.5 | 0 / 1 | |
| 1.2.4 | 0 / 1 | |
| 1.2.3 | 0 / 1 | |
| 1.2.2 | 0 / 1 | |
| 1.2.1 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.9 | 0 / 1 | |
| 1.1.8 | 0 / 1 | |
| 1.1.7 | 0 / 1 | |
| 1.1.6 | 0 / 1 | |
| 1.1.5 | 0 / 1 | |
| 1.1.4 | 0 / 1 | |
| 1.1.3 | 0 / 1 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.10 | 0 / 1 | |
| 1.0.9 | 0 / 1 | |
| 1.0.8 | 0 / 1 | |
| 1.0.7 | 0 / 1 | |
| 1.0.2 | 0 / 1 | |
| 1.0.1 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.11
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.10
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsMaintainer email 'https://www.tenancy.co.nz' uses domain 'https://www.tenancy.co.nz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.