@tinacms/sharedctx
This package is only used internally and is for sharing context from non edit mode and edit mode. This package should be **very** small as it will end it up the users production bundle.
2
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
wicksipediawarwick_tinacmskldavis4scottgallantjeffsee55
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org maintainer rotation on established monorepo package, no code changes accompany it. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with maintainer rotation, not takeover; diff shows no material changes. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-running monorepo package with sporadic releases; no suspicious diff accompanies it. | ai |
v1.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.