@orion-js/helpers
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo subpackage with no description across its history; real 85-version framework helper, not a throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals (no repo/keywords/desc) are stable monorepo traits; package has 1.2k weekly dl and 7 inbound deps. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore attestation is consistent across versions; not a regression. | ai |
v4.4.0
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): 1756-day dormancy followed by publisher change is a canonical account-takeover pattern.) This package had no publishes for over 6 months before this version. Long dormancy followed by sudden activity can indicate account takeover.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.