@omnia/management-system
Omnia Management System.
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): New publisher matched as known maintainer by email; not a real takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Longstanding thin package structure unchanged across 543 versions. | ai |
Versions (showing 80 of 80)
| 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.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.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.1 | 0 / 0 | |
| 7.8.0 | 0 / 0 | |
| 7.7.8 | 0 / 0 | |
| 7.7.7 | 0 / 0 | |
| 7.7.6 | 0 / 0 | |
| 7.7.5 | 0 / 0 | |
| 7.7.4 | 0 / 0 | |
| 7.7.3 | 0 / 0 | |
| 7.7.2 | 0 / 0 | |
| 7.7.1 | 0 / 0 | |
| 7.7.0 | 0 / 0 | |
| 7.6.26 | 0 / 0 | |
| 7.6.25 | 0 / 0 | |
| 7.6.24 | 0 / 0 | |
| 7.6.23 | 0 / 0 | |
| 7.6.22 | 0 / 0 | |
| 7.6.21 | 0 / 0 | |
| 7.6.20 | 0 / 0 | |
| 7.6.19 | 0 / 0 | |
| 7.6.18 | 0 / 0 | |
| 7.6.17 | 0 / 0 | |
| 7.6.16 | 0 / 0 | |
| 7.6.15 | 0 / 0 | |
| 7.6.14 | 0 / 0 | |
| 7.6.13 | 0 / 0 | |
| 7.6.12 | 0 / 0 | |
| 7.6.11 | 0 / 0 | |
| 7.6.10 | 0 / 0 | |
| 7.6.8 | 0 / 0 | |
| 7.6.6 | 0 / 0 | |
| 7.6.5 | 0 / 0 | |
| 7.6.4 | 0 / 0 | |
| 7.6.3 | 0 / 0 | |
| 7.6.2 | 0 / 0 | |
| 7.6.1 | 0 / 0 | |
| 7.6.0 | 0 / 0 | |
| 7.5.17 | 0 / 0 | |
| 7.5.16 | 0 / 0 | |
| 7.5.15 | 0 / 0 | |
| 7.5.14 | 0 / 0 | |
| 7.5.13 | 0 / 0 | |
| 7.5.12 | 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.8
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.7
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-11, 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.6
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-01-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.5
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-01-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.4
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 2024-12-31, 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.3
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 2024-12-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.2
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 2024-12-10, 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.1
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 2024-12-03, 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.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 2024-11-28, 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.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.