Repository navigation
chore(ci): add secret, workflow and changed-code audits; harden installs - #191
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the repo in line with unlockers-io/standy#209.
.githubandpnpm fallow:audit, which fails only on complexity, duplication or dead code introduced by the PR (the script is now barefallow audit, because a PR checkout has no localmain)..fallowrc.jsongets boundaries: packages can't import apps, and apps can't import each other.trustPolicy: no-downgrade, with exact-version excludes. Each one was checked against its publish history; the next release of each package still has to meet the policy:semver@6.3.1: a 6.x backport published by hand after 7.x had provenancewhy-is-node-running@3.2.2: published by hand by the same maintainer in Jan 2025; 3.2.3 has trusted publishingnoImplicitOverrideandnoFallthroughCasesInSwitch.Validated locally:
standy check(against the new standard), typecheck, gitleaks, zizmor, and the repo's lint/format checks all pass.