@omnia/workplace
Omnia Workplace.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Provenance confirms andtii is a known maintainer email match, not a hijack. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-standing type-definitions/meta package with 2053 versions; empty stub is expected. | ai |
Versions (showing 51 of 105)
| Version | Deps | Published |
|---|---|---|
| 7.11.19 | 0 / 0 | |
| 7.11.18 | 0 / 0 | |
| 7.11.17 | 0 / 0 | |
| 7.11.16 | 0 / 0 | |
| 7.11.15 | 0 / 0 | |
| 7.11.14 | 0 / 0 | |
| 7.11.13 | 0 / 0 | |
| 7.11.12 | 0 / 0 | |
| 7.11.11 | 0 / 0 | |
| 7.11.10 | 0 / 0 | |
| 7.11.9 | 0 / 0 | |
| 7.11.8 | 0 / 0 | |
| 7.11.7 | 0 / 0 | |
| 7.11.6 | 0 / 0 | |
| 7.11.5 | 0 / 0 | |
| 7.11.4 | 0 / 0 | |
| 7.11.3 | 0 / 0 | |
| 7.11.2 | 0 / 0 | |
| 7.11.1 | 0 / 0 | |
| 7.9.43 | 0 / 0 | |
| 7.9.42 | 0 / 0 | |
| 7.9.41 | 0 / 0 | |
| 7.9.14 | 0 / 0 | |
| 7.9.13 | 0 / 0 | |
| 7.9.12 | 0 / 0 | |
| 7.9.11 | 0 / 0 | |
| 7.9.6 | 0 / 0 | |
| 7.9.5 | 0 / 0 | |
| 7.9.4 | 0 / 0 | |
| 7.9.3 | 0 / 0 | |
| 7.9.2 | 0 / 0 | |
| 7.9.1 | 0 / 0 | |
| 7.9.0 | 0 / 0 | |
| 7.8.12 | 0 / 0 | |
| 7.8.11 | 0 / 0 | |
| 7.8.10 | 0 / 0 | |
| 7.8.9 | 0 / 0 | |
| 7.8.8 | 0 / 0 | |
| 7.8.7 | 0 / 0 | |
| 7.8.6 | 0 / 0 | |
| 7.8.5 | 0 / 0 | |
| 7.8.4 | 0 / 0 | |
| 7.8.3 | 0 / 0 | |
| 7.8.2 | 0 / 0 | |
| 7.8.0 | 0 / 0 | |
| 7.7.15 | 0 / 0 | |
| 7.7.14 | 0 / 0 | |
| 7.7.13 | 0 / 0 | |
| 7.7.12 | 0 / 0 | |
| 7.7.11 | 0 / 0 | |
| 7.7.10 | 0 / 0 |
v7.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-04-22, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.15
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-04-08, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.14
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-03-25, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.13
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-03-18, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.12
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-02-25, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.11
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-02-18, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.7.10
3 findingsAll previous maintainers (omnia) were replaced by new maintainers (andtii). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andtii) than the most recent previously approved version (omnia) on 2025-02-12, but andtii is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.