@quintype/framework
Libraries to help build Quintype Node.js apps
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Large org package; maintainer churn is routine team management, not a takeover signal. | ai | |
| phantom-deps | phantom-dep:atob | AI (phantom-deps): Declared dependency used indirectly via config/polyfill; stable for this package. | ai | |
| phantom-deps | phantom-dep:firebase | AI (phantom-deps): Optional integration dependency declared for downstream consumers; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jsdoc/salty | AI (phantom-deps): Used by jsdoc tooling referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): Used via overrides/config for grpc compatibility; stable false positive. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires only in docs-src/publish.js (jsdoc tooling), not in runtime framework code; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:get-youtube-id | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mocha-snapshots | AI (phantom-deps): Test tooling referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:babel-plugin-react-css-modules | AI (phantom-deps): Babel plugin referenced in config files; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quintype/seo | AI (phantom-deps): Same-org package used indirectly; stable false positive for this framework. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.36.0 | 32 / 35 | |
| 7.35.1 | 32 / 35 | |
| 7.35.0 | 32 / 35 | |
| 7.34.14 | 32 / 35 | |
| 7.34.13 | 32 / 35 | |
| 7.34.11 | 32 / 35 | |
| 7.34.9 | 32 / 35 | |
| 7.34.8 | 32 / 35 | |
| 7.34.7 | 32 / 35 | |
| 7.34.6 | 32 / 35 | |
| 7.34.5 | 32 / 35 | |
| 7.34.4 | 32 / 35 | |
| 7.34.3 | 32 / 35 | |
| 7.34.2 | 32 / 35 | |
| 7.34.1 | 32 / 35 |
v7.36.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (reena07111996) than the most recent previously approved version (veena.yemmiganur) on 2026-06-03, but reena07111996 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.35.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (reena07111996) than the most recent previously approved version (veena.yemmiganur) on 2026-04-22, but reena07111996 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (reena07111996) than the most recent previously approved version (veena.yemmiganur) on 2026-04-13, but reena07111996 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.34.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.34.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-01-05, but veena.yemmiganur is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.8
2 findingsThis version was published by a different npm account than previous versions on 2025-11-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.34.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2025-10-17, but veena.yemmiganur is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.5
2 findingsThis version was published by a different npm account than previous versions on 2025-09-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.34.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (veena.yemmiganur) than the most recent previously approved version (reena07111996) on 2025-07-21, but veena.yemmiganur is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.34.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vishwanath.reddy) than the most recent previously approved version (reena07111996) on 2025-06-25, but vishwanath.reddy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.